lkml.org 
[lkml]   [2011]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC/PULL 00/11] introduce export.h; reduce module.h usage
Hi Paul,

On Thu, 28 Jul 2011 11:42:29 -0400 Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
>
> [Re: [RFC/PULL 00/11] introduce export.h; reduce module.h usage] On 28/07/2011 (Thu 09:15) Ingo Molnar wrote:
>
> > * Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> >
> > > I don't think there really is any rocket science or contentious
> > > stuff here. It is a sensible cleanup that adds organization and
> > > speeds up compiles. The RFC I'm hoping for is more about how/when
> > > we want to get this in tree.
> >
> > I'd suggest to stick it into linux-next ASAP, leave there for a few
> > days and after fixing any potential fallout send it Linuswards.
>
> Hi Stephen,
>
> Would you please add this to linux-next?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux.git#module.h-split

OK, I will add it today.

> It won't need to be there forever, just long enough to shake loose
> anyone who has implicitly been using module.h without asking for it.

Please remind me to remove it again after you are finished with it.
There is no real hurry about that as once Linus' merges it, it has very
little effect on my process (assuming that you get him to merge the
actual commits that are in my tree - hint, hint :-)).

Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgment of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing 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 if you deem it necessary.

--
Cheers,
Stephen Rothwell
sfr@canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees. You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next. These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc. The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc. If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2011-07-29 03:23    [W:0.057 / U:3.208 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site