From: Andi Kleen <andi@firstfloor•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Andi Kleen <andi@firstfloor•org>,
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 11:55:35 +0200 [thread overview]
Message-ID: <20090810095535.GB6838@basil.fritz.box> (raw)
In-Reply-To: <20090810194528.a3bc0cbc.sfr@canb.auug.org.au>
> OK, I have added this today.
Thanks.
> 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)
all true for hwpoison.
>
> *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
This is practially all generic MM or VFS code, nothing for Ingo.
The only part that should concern anything Ingo maintains
is a one tiny patch for x86 in the patch series. While that could
be in theory separated out I don't think it makes too much sense
(the patch wouldn't build without the rest of hwpoison)
-Andi
--
ak@linux•intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-08-10 9:55 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 ` hwpoison merge for linux-next / 2.6.32 Stephen Rothwell
2009-08-10 9:55 ` Andi Kleen [this message]
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=20090810095535.GB6838@basil.fritz.box \
--to=andi@firstfloor$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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