From: Andrew Morton <akpm@osdl.org>
To: Paul Jackson <pj@sgi.com>
Cc: ashok.raj@intel.com, davidm@hpl.hp.com,
linux-kernel@vger.kernel.org, anil.s.keshavamurthy@intel.com,
jreiser@BitWagon.com, mike@navi.cx, pageexec@freemail.hu,
colpatch@us.ibm.com, wli@holomorphy.com, rusty@rustcorp.com.au,
nickpiggin@yahoo.com.au
Subject: Re: various cpu patches [was: (resend) take3: Updated CPU Hotplug patches]
Date: Wed, 5 May 2004 00:14:25 -0700 [thread overview]
Message-ID: <20040505001425.6d4e8562.akpm@osdl.org> (raw)
In-Reply-To: <20040505000348.018f88bb.pj@sgi.com>
Paul Jackson <pj@sgi.com> wrote:
>
> Hmmm .. we're getting backed up here. Sure glad Andrew's got the job of
> conducting this, not me ...
>
> The purpose of this message is to list several patches that are
> interacting, and the order that I'm guessing Andrew will end up taking
> them. I claim no authority, and at best very limited forecasting
> ability.
I try to keep patches in the expected merge-up order. The patching order
is in the series file - see the `patch-series' symlink in the kerne.org
directory.
> This is just to put a source of possible confusions on the table,
> by running it up the flagpole, and inviting the shooting to begin.
>
> The following patches are colliding or interacting, listed in the order
> that I'm guessing they will end up going into *-mm, and with my guess of
> their current status:
>
> 1. Nick Piggin's sched_domains patches (in *-mm now)
> 2. Ashok Raj's CPU Hotplug patches for IA64 (sent back to author for repair)
> 3. Paul Jackson's bitmap/cpumask cleanup (in my workarea ready to submit)
> 4. John Reiser's bssprot (unrelated, except for ia64 friendly fire damage)
> 5. Matthew Dobson's nodemask_t (in Matthew's workarea, ready to submit)
> 6. Andi Kleen's numa placement (being reviewed now, I think)
Planned for shortly after 2.6.6 are:
sched-domains
rmap 7-14 (15-23 probably a week later)
numa api
> Actually, bssprot is independent, once it resolves some ia64 issue, and
> the last two (nodemask and numa) are sufficiently independent to go
> in parallel or reverse order.
I dropped bssprot - it was causing too much grief.
> If you _wanted_, Andrew, to add to your current patch load, I'd be
> delighted to submit my final bitmap/cpumask cleanup now - I'm just
> guessing that you will politely ignore my offer.
I confess to being vaguely stunned that it is possible to generate a ~20
patch series againt the bitmap code. I'll pay more attention next time it
flies past.
next prev parent reply other threads:[~2004-05-05 7:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 4:17 (resend) take3: Updated CPU Hotplug patches for IA64 (pj blessed) Patch [6/7] Ashok Raj
2004-05-05 5:59 ` Andrew Morton
2004-05-05 7:03 ` various cpu patches [was: (resend) take3: Updated CPU Hotplug patches] Paul Jackson
2004-05-05 7:14 ` Andrew Morton [this message]
2004-05-05 7:28 ` Paul Jackson
2004-05-05 7:24 ` William Lee Irwin III
2004-05-05 7:44 ` Paul Jackson
2004-05-05 7:52 ` William Lee Irwin III
2004-05-05 7:44 ` (resend) take3: Updated CPU Hotplug patches for IA64 (pj blessed) Patch [6/7] Nick Piggin
2004-05-05 14:07 ` Ashok Raj
2004-05-05 17:47 ` (resend-2) " Ashok Raj
2004-05-06 6:13 ` Andrew Morton
2004-05-06 9:32 ` (resend-3) " Ashok Raj
2004-05-06 9:45 ` Andrew Morton
2004-05-06 9:54 ` Ashok Raj
2004-05-05 17:50 ` (resend-2) take3: Updated CPU Hotplug patches for IA64 (pj blessed) Patch [7/7] Ashok Raj
2004-05-11 23:16 ` (resend) take3: Updated CPU Hotplug patches for IA64 (pj blessed) Patch [6/7] Paul Jackson
2004-05-11 23:38 ` Andrew Morton
2004-05-11 23:55 ` Paul Jackson
2004-05-11 23:58 ` Ashok Raj
2004-05-12 0:37 ` Andrew Morton
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=20040505001425.6d4e8562.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ashok.raj@intel.com \
--cc=colpatch@us.ibm.com \
--cc=davidm@hpl.hp.com \
--cc=jreiser@BitWagon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@navi.cx \
--cc=nickpiggin@yahoo.com.au \
--cc=pageexec@freemail.hu \
--cc=pj@sgi.com \
--cc=rusty@rustcorp.com.au \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®