Hi Robert, On Thu, 30 Jul 2009 14:07:38 +0200 Robert Richter <robert.richter@xxxxxxx> wrote: > > please add following tree to linux-next: > > git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git for-next > > This is the oprofile master branch containing all changes for the next > merge window. Added from today. > The general way of sending oprofile to linux-next is via tip. So, this > will be a temporary solution until Ingo will be back. I added it after the tip tree, so if it hangs around for a few days after Ingo has integrated it, it should not be a problem. 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 in this case, Ingo, (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:
pgpPoS3Kq4xcv.pgp
Description: PGP signature
