From: Stephen Rothwell <sfr@canb•auug.org.au>
To: michal.simek@petalogix•com
Cc: Andrew Morton <akpm@linux-foundation•org>,
Arnd Bergmann <arnd@arndb•de>,
John Williams <john.williams@petalogix•com>,
linux-next@vger•kernel.org
Subject: Re: Microblaze merge
Date: Wed, 27 May 2009 18:10:22 +1000 [thread overview]
Message-ID: <20090527181022.f69d7036.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4A1CEA3C.1050904@petalogix.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
HI Michal,
On Wed, 27 May 2009 09:22:36 +0200 Michal Simek <michal.simek@petalogix•com> 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@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-27 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 7:22 Microblaze merge Michal Simek
2009-05-27 8:10 ` Stephen Rothwell [this message]
2009-05-27 13:06 ` Michal Simek
2009-05-27 13:24 ` Stephen Rothwell
2009-05-27 13:33 ` Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090527181022.f69d7036.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=john.williams@petalogix$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=michal.simek@petalogix$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox