ling list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased
HI Chris,
On Wed, 26 Oct 2011 17:23:22 -0400 Chris Ball wrote:
>
> The mmc-next tree has returned to its original location at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git mmc-next
I have switched to that now.
--
Cheers,
Stephen Rothwell
Hi Chris,
On Wed, 21 Sep 2011 13:49:49 -0400 Chris Ball wrote:
>
> Please switch the mmc-next location for linux-next over to:
>
> git://dev.laptop.org/users/cjb/mmc mmc-next
OK, I have switched from today.
--
Cheers,
Stephen Rothwells...@canb.auug
her error.
>
> commit d9c927833a42b4eaae4addd031f780f4530f7a2d
> Author: Arnaud Patard (Rtp)
> Date: Fri Aug 5 09:32:41 2011 +0200
>
> iMX: Fix build for iMX53
That is included in today's linux-next.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
http://www.canb.auug.org.
it. (Linus released it, but it
> has not been available with 'git fetch' yet.)
It could well be an interaction with the module.h split up, in which case
it will only appear in linux-next. That said, I don;t get that error in
my manual builds, so the config (or at least ARCH) could
should remove the mmc tree (currently empty) from
linux-next, then?
> I actually pretend to maintain a huge number of subsystems and should
> sprinkle akpms all over MAINTAINERS so stuff doesn't get lost.
How about splitting these subsystems out of -mm and adding them to
linux-n
