From: Li Zefan <lizf@cn.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: miaox@cn.fujitsu.com, linux-kernel@vger.kernel.org, pj@sgi.com,
menage@google.com
Subject: Re: [PATCH 1/2] cpusets: restructure the function update_cpumask() and update_nodemask()
Date: Wed, 04 Jun 2008 08:55:43 +0800 [thread overview]
Message-ID: <4845E80F.5000808@cn.fujitsu.com> (raw)
In-Reply-To: <20080603150346.4611b5ab.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Mon, 02 Jun 2008 16:31:05 +0800
> Miao Xie <miaox@cn.fujitsu.com> wrote:
>
>> extract two functions from update_cpumask() and update_nodemask().They will be
>> used later for updating tasks' cpus_allowed and mems_allowed after CPU/NODE
>> offline/online.
>
> Unfortunately this patch conflicts with
> http://userweb.kernel.org/~akpm/mmotm/broken-out/cpusets-fix-bug-when-adding-nonexistent-cpu-or-mem.patch
>
> Please check that the patch which I merged still makes sense. ie: that
> we did not revert the effects of that bugfix.
>
They are fixing 2 different bugs, so they are irrelated, but unfortunately conflict in
the code due to Miao's first patch which does code restructuring.
next prev parent reply other threads:[~2008-06-04 0:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 8:31 [PATCH 1/2] cpusets: restructure the function update_cpumask() and update_nodemask() Miao Xie
2008-06-02 9:55 ` Paul Jackson
2008-06-03 22:03 ` Andrew Morton
2008-06-04 0:55 ` Li Zefan [this message]
2008-06-04 2:00 ` Miao Xie
2008-06-04 2:11 ` Andrew Morton
2008-06-04 2:16 ` Li Zefan
2008-06-04 2:59 ` Paul Jackson
2008-06-04 4:00 ` Andrew Morton
2008-06-04 4:02 ` Andrew Morton
2008-06-04 4:07 ` Paul Jackson
2008-07-02 9:19 ` Andrew Morton
2008-07-02 9:41 ` Li Zefan
2008-07-02 9:54 ` Li Zefan
-- strict thread matches above, loose matches on Subject: below --
2008-06-04 2:03 Miao Xie
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=4845E80F.5000808@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=miaox@cn.fujitsu.com \
--cc=pj@sgi.com \
/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