Today's linux-next build (x86_64 allmodconfig) failed like this:

drivers/mfd/htc-pasic3.c:22:31: error: asm/arch/pxa-regs.h: No such file or=
 directory

I have reverted commit 5dc3339aa5ba29593ea57814049ddca8c12831c8 ("[ARM]
4964/1: htc-pasic3: MFD driver for PASIC3 LED control + DS1WM chip") as
the easiest thing.

Russell, this is why I would have liked you to participate in the
linux-next tree ...

--=20
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[ message continues ]

That's known from the -mm tree since last week.  It's not the only thing
that's wrong.

I had asked Linus on Monday morning _not_ to pull my tree because there's
various problems with it.  Unfortunately, though Linus didn't see that
before he pulled it and I now have a rapidly growing set of fixes.

It will be towards the end of this week before I'll be able to finish

linux-next will not give me anything which -mm isn't giving me.  As I
said in the discussion, linux-next value is _very_ small for me.

Sorry but true.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:
--

[ message continues ]

From: Russell King <rmk+lkml@arm.linux.org.uk>

Thank you for your participation in the community. :-/

--

[ message continues ]

Putting arm into linux-next means that Stephen (and git) handle the merges
rather than having me (and not-git) do it.  Which helps me.

I expect that linux-next will get a lot more cross-compilation testing than
-mm.  Which helps you.
--

[ message continues ]

Hi Russell,

On Tue, 22 Apr 2008 08:36:22 +0100 Russell King <rmk+lkml@arm.linux.org.uk>=

Let me try again (others may want to read as well).

What you get:
	- 5 times a week your tree gets merged with lots of other code
	  destined for Linus' next release.  From this you get to find
	  out about things in other trees that clash with yours.
	- This tree gets built on several architectures for several configs
	  (including arm).  So you find out if other trees will break yours.
	- I am happy to build more (basically all) the arm configs as I
	  have offered before.

What others get:
	- You get told if your changes clash or break other's changes.
	- They get told if your tree may require changes to theirs.

What it costs:
	- you need to create a tree (o quilt series) that contains the
	  changes you expect to submit to Linus in the next merge window.
	  This is not so different from the tree you currently send to
	  Andrew (and is probably a subset of that). You update this tree
	  as you want to and I fetch it at least daily.
	- Reading a few extra emails if/when I find problems that may
	  concern you.

Thanks for listening.
--=20
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
[ message continues ]

But it would help all of the rest of us out immensely.  From what I can
tell (please correct me if I'm wrong), the linux-arm tree isn't
publicly seen by anyone else so they know exactly what they need to
rebase off of to submit patches for to you.  Getting your stuff into
linux-next would provide a public place for others to base off of,
making it easier for them to send patches to you ensuring that they
apply properly.

Which in the end, will help others be able to contribute easier, and
help you by getting patches you do not need to rebase yourself.

thanks,

greg k-h
--

[ message continues ]