lkml.org 
[lkml]   [2011]   [Jun]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCHES v3] pci/of: Generic PCI <-> OF matching
Hi Ben,

On Wed, 08 Jun 2011 10:06:05 +1000 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> On Wed, 2011-06-08 at 07:37 +1000, Benjamin Herrenschmidt wrote:
> > > > No significant changes (other than a rebase) nor new feedback since last
> > > > time, I've also added a few acks I got. But not worth spamming the list
> > > > with a re-post.
> > > >
> > > > I'd like this to go into -next now so it can hit the next merge window,
> > > > unless somebody objects.
> > > >
> > > > I've put the series in a branch "of-pci" of my powerpc.git repo at:
> > > >
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git of-pci
> > > >
> > > > Please let me know if you're ok (and maybe give me Ack's) and I'll ask
> > > > Stephen to add it to next.
> > >
> > > Yeah, the generic bits look good to me, you can add my
> > > Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> >
> > Great. Will do. I'll ask Stephen to that that in -next then and will ask
> > Linus to pull directly at the next merge window, separately from
> > powerpc.git (tho I might actually end up pulling that tree into
> > powerpc.git too as I might end up with stuff that depends on it).
>
> Allright, Stephen, can you stick this into -next please ?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git of-pci
>
> I've added Jesse's acks.

OK, I have added this today.

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-06-08 02:31    [from the cache]
©2003-2011 Jasper Spaans