From: Paul Jackson <pj@sgi.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: akpm@osdl.org, 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, 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:44:56 -0700 [thread overview]
Message-ID: <20040505004456.4fd397f0.pj@sgi.com> (raw)
In-Reply-To: <20040505072431.GG1397@holomorphy.com>
> I don't see any essential interaction between these patches.
Essentially, yes. The interactions were:
Ashok's Hotplug added an essential arch-specific ifdef to a
arch-specific cpumask file that my cleanup removes - so I had
to work with Ashok to remove that arch dependency.
Reiser's bssprot broke ia64, so I couldn't test with that patch.
Matthew has recoded his nodemask patch to presume my cpumask cleanup.
Andi's numa patch is so far as we know independent, but close enough
to all this other activity to be at risk for something.
The interactions were enough that I probably couldn't expect Andrew to
wade through them to adapt my cleanup. Rather I pretty much have to
deliver my cleanup ready to go, with whatever Andrew thinks is his
current *-mm series.
I'll be doing well just to get Andrew to look at it, despite what I take
to be endorsements from Matthew, Rusty and Joe Korty, and conditional
acceptance from yourself. Andrew would probably drop it in a heartbeat
if it collided non-trivially.
So merge work - yes. But merge work that mostly I need to do, which
makes me very sensitive to the order in which things happen.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-05-05 7:49 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
2004-05-05 7:28 ` Paul Jackson
2004-05-05 7:24 ` William Lee Irwin III
2004-05-05 7:44 ` Paul Jackson [this message]
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=20040505004456.4fd397f0.pj@sgi.com \
--to=pj@sgi.com \
--cc=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=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 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.