Hi Boris, On Fri, 15 May 2009 15:07:29 +0200 Borislav Petkov <borislav.petkov@xxxxxxx> wrote: > > can you please add the tree at > > git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git for-next > > to linux-test for a wider testing. It is rebased ontop of > 45d447406a19cbfd42720f066f156f4eb9d68801 (Linus's tree from yesterday). A hint as to what the tree is about would be nice. It looks like EDAC stuff (mostly AMD64). If so, you are not listed as a maintainer of that code (Doug cc'd). The boilerplate: What I tell everyone: all patches/commits in the tree/series must have been: posted to a relevant mailing list reviewed unit tested destined for the next merge window (or the current release) *before* they are included. The linux-next tree is for integration testing and to lower the impact of conflicts between subsystems in the next 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@xxxxxxxxxxxxxxxx http://www.canb.auug.org.au/~sfr/
Attachment:
pgpF0cWErmeVc.pgp
Description: PGP signature
