From: Paul Jackson <pj@sgi.com>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, menage@google.com,
a.p.zijlstra@chello.nl, vegard.nossum@gmail.com,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [PATCH] cpuset: Rework sched domains and CPU hotplug handling (2.6.27-rc1)
Date: Sat, 2 Aug 2008 06:39:00 -0500 [thread overview]
Message-ID: <20080802063900.6615e5ca.pj@sgi.com> (raw)
In-Reply-To: <1217631552-22129-1-git-send-email-maxk@qualcomm.com>
The Subject line suggests that this latest version of your patch should
apply on top of 2.6.27-rc1. That does not seem to be quite accurate.
As stated in your previous message, it seems you're working on top of
Linus's latest git version, which, at least for the source file
kernel/cpuset.c, is (I suppose) more or less the same as 2.6.27-rc1
plus the 'origin.patch' that is at the top of Andrew's broken out quilt
patch series 2.6.27-rc1-mm1.
That origin.patch includes Li Zefan's patch:
cpuset: clean up cpuset hierarchy traversal code
which Andrew recently sent along to Linus, and which patch is presumed
by this latest version of your patch.
I'll take a further look at your patch now.
We have lots of trees, including various from Ingo, linux-next, Andrew,
and Linus, each in many versions. It helps others if you can state
exactly what tree/version a patch applies to, in each patch version
that you submit.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-08-02 11:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 22:59 [PATCH] cpuset: Rework sched domains and CPU hotplug handling (2.6.27-rc1) Max Krasnyansky
2008-08-02 11:39 ` Paul Jackson [this message]
2008-08-02 16:32 ` Max Krasnyansky
2008-08-03 3:51 ` Paul Jackson
2008-08-03 18:07 ` Max Krasnyansky
2008-08-04 6:00 ` Paul Jackson
2008-08-04 22:11 ` Max Krasnyansky
2008-08-05 3:56 ` Paul Jackson
2008-08-05 20:30 ` Max Krasnyansky
2008-08-05 23:05 ` Paul Jackson
2008-08-06 3:24 ` Max Krasnyansky
2008-08-06 3:29 ` Paul Jackson
2008-08-06 3:53 ` Max Krasnyansky
2008-08-06 4:28 ` Paul Jackson
2008-08-06 5:03 ` Max Krasnyansky
2008-08-06 5:46 ` Paul Jackson
2008-08-06 20:20 ` Max Krasnyansky
2008-08-06 20:29 ` Paul Jackson
2008-08-06 20:30 ` Paul Menage
2008-08-06 20:56 ` Paul Jackson
2008-08-06 20:36 ` Max Krasnyansky
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=20080802063900.6615e5ca.pj@sgi.com \
--to=pj@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=maxk@qualcomm.com \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=vegard.nossum@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.