From: Andi Kleen <ak@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
Chuck Ebbert <76306.1226@compuserve.com>,
Zachary Amsden <zach@vmware.com>,
Jan Beulich <jbeulich@novell.com>,
James Bottomley <James.Bottomley@steeleye.com>,
Matt Tolentino <matthew.e.tolentino@intel.com>
Subject: Re: [PATCH 1/6] Initialize the per-CPU data area.
Date: Mon, 25 Sep 2006 23:05:10 +0200 [thread overview]
Message-ID: <200609252305.10239.ak@suse.de> (raw)
In-Reply-To: <45184318.6060807@goop.org>
On Monday 25 September 2006 22:59, Jeremy Fitzhardinge wrote:
> Andi Kleen wrote:
> > If this is really 1/1 why does it patch a file called pda.h?
> >
> > I've thrown away the local pda patches before this because I assumed
> > you started fresh.
> >
> > Somehow I'm not surprised that nothing applies. You seem to always
> > start with some random tree that nobody else has.
> >
> Well, it's based on -mm, but I guess that includes pieces of your patch
> series. I was a bit surprised to see pda.h still in -mm with the rest
> dropped.
I see. Andrew reverted some stuff to fix his PII (which I broke BTW
it wasn't a problem in your original patches) but he didn't revert everything
only starting from the bisected patch.
Ok on the next resync everything will be dropped there.
> > Anyways, this patchkit has caused so much trouble and churn that I'll drop
> > it for now until after the .19 merge is done.
> >
> I'll respin it against your patches later today.
Thanks. It's not that urgent because the merge will need a few days
at least.
Also I must admit I haven't figured out yet if yours or Rusty's patchkit
is better. So far I was leaning towards yours, but that might be because
I haven't looked closely at Rusty's version.
-Andi
next prev parent reply other threads:[~2006-09-25 21:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 18:45 [PATCH 0/6] Per-processor private data areas for i386 jeremy
2006-09-25 18:45 ` [PATCH 1/6] Initialize the per-CPU data area jeremy
2006-09-25 20:49 ` Andi Kleen
2006-09-25 20:59 ` Jeremy Fitzhardinge
2006-09-25 21:05 ` Andi Kleen [this message]
2006-09-25 21:33 ` Jeremy Fitzhardinge
2006-09-25 18:45 ` [PATCH 2/6] Use %gs as the PDA base-segment in the kernel jeremy
2006-09-25 18:45 ` [PATCH 3/6] Fix places where using %gs changes the usermode ABI jeremy
2006-09-25 18:45 ` [PATCH 4/6] Update sys_vm86 to cope with changed pt_regs and %gs usage jeremy
2006-09-25 18:45 ` [PATCH 5/6] Implement smp_processor_id() with the PDA jeremy
2006-09-25 18:45 ` [PATCH 6/6] Implement "current" " jeremy
2006-09-27 19:46 ` [PATCH 0/6] Per-processor private data areas for i386 Pavel Machek
2006-09-27 20:28 ` Jeremy Fitzhardinge
2006-09-27 20:28 ` Jeremy Fitzhardinge
2006-09-29 0:22 ` Rusty Russell
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=200609252305.10239.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=zach@vmware.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.