From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andi Kleen <andi@firstfloor•org>
Cc: akpm@linux-foundation•org, linux-next@vger•kernel.org,
LKML <linux-kernel@vger•kernel.org>
Subject: Re: hwpoison merge for linux-next / 2.6.32
Date: Mon, 10 Aug 2009 19:45:28 +1000 [thread overview]
Message-ID: <20090810194528.a3bc0cbc.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090807084902.GA14309@basil.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
Hi Andi,
On Fri, 7 Aug 2009 10:49:02 +0200 Andi Kleen <andi@firstfloor•org> wrote:
>
> Could you please pull git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-mce-2.6.git hwpoison
> into linux-next?
>
> hwpoison is the VM part of extended memory error handling.
>
> This tree has been extensively reviewed now and people seem to be happy now and is
> imho ready for merge.
>
> Andrew also indicated earlier he would merge it for .32.
OK, I have added this today.
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.
> How do you want to handle it. Will you take it and send or should I send direct
> pull requests to Linus during the merge window?
Andrew, If you have other plans, just yell.
--
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 parent reply other threads:[~2009-08-10 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090807084902.GA14309@basil.fritz.box>
2009-08-10 9:45 ` Stephen Rothwell [this message]
2009-08-10 9:55 ` hwpoison merge for linux-next / 2.6.32 Andi Kleen
2009-08-10 10:00 ` Stephen Rothwell
2009-08-10 10:06 ` Andi Kleen
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=20090810194528.a3bc0cbc.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=andi@firstfloor$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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