From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <andrea@novell.com>, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Dropped patch: mm/mempolicy.c:sp_lookup()
Date: Wed, 17 Nov 2004 02:00:20 +0100 [thread overview]
Message-ID: <20041117010020.GF2392@wotan.suse.de> (raw)
In-Reply-To: <200411152318_MC3-1-8EBD-DEEE@compuserve.com>
On Mon, Nov 15, 2004 at 11:15:51PM -0500, Chuck Ebbert wrote:
> Andrea posted this one-liner a while ago as part of a larger patch. He said
> it fixed return of the wrong policy in some conditions. Was this a valid fix?
Yes it was.
-Andi
next prev parent reply other threads:[~2004-11-17 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 4:15 Dropped patch: mm/mempolicy.c:sp_lookup() Chuck Ebbert
2004-11-17 1:00 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-17 3:54 Chuck Ebbert
2004-11-17 12:08 ` Andi Kleen
2004-11-17 19:13 ` Andrew Morton
2004-11-17 20:06 ` Hugh Dickins
2004-11-17 20:21 ` Andrew Morton
2004-11-17 20:29 ` Andrew Morton
2004-11-18 5:05 ` Andi Kleen
2004-11-18 3:08 ` Andrea Arcangeli
2004-11-18 3:08 ` Andrea Arcangeli
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=20041117010020.GF2392@wotan.suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=andrea@novell.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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