HI Michal, On Wed, 27 May 2009 09:22:36 +0200 Michal Simek <michal.simek@xxxxxxxxxxxxx> wrote: > > Can you please merge my next branch to linux-next? > > The following changes since commit 5805977e63a36ad56594a623f3bd2bebcb7db233: > Linus Torvalds (1): > Merge branch 'for-linus' of git://git.kernel.org/.../jbarnes/drm-2.6 > > are available in the git repository at: > > git://git.monstr.eu/linux-2.6-microblaze.git next I have added it to the end of the tree for today (you just caught me in time :-)). Tomorrow it will be moved back with all the other architectures. 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:
pgpYDnEcK5fF7.pgp
Description: PGP signature
