From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] resend, cpuset/hotplug fixes
Date: Thu, 10 Sep 2009 21:13:45 +0200 [thread overview]
Message-ID: <20090910191345.GA32635@redhat.com> (raw)
The 1st patch is preparation. 2-3 fix different problems, the 3rd one
depends on 2nd.
These patches change the code which I don't really understand, please
review.
As for the 3rd patch, it replaces
cpu_hotplug-dont-affect-current-tasks-affinity.patch
in -mm tree. Imho the new patch is more simple and clean, but of course
this is subjective and I am biased.
Oleg.
next reply other threads:[~2009-09-10 19:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 19:13 Oleg Nesterov [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-10 19:21 [PATCH 0/3] resend, cpuset/hotplug fixes Oleg Nesterov
2009-09-10 20:18 ` Rafael J. Wysocki
2009-09-10 20:53 ` Peter Zijlstra
2009-09-11 7:15 ` Lai Jiangshan
2009-09-11 7:33 ` Peter Zijlstra
2009-09-11 7:53 ` Lai Jiangshan
2009-09-11 7:57 ` Peter Zijlstra
2009-09-11 7:37 ` Peter Zijlstra
2009-09-11 18:03 ` Oleg Nesterov
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=20090910191345.GA32635@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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