From: Andrew Morton <akpm@linux-foundation.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [VOYAGER] fix build broken by shift to smp_ops
Date: Mon, 14 May 2007 13:37:45 -0700 [thread overview]
Message-ID: <20070514133745.5bfc34ac.akpm@linux-foundation.org> (raw)
In-Reply-To: <4648C062.5090704@goop.org>
On Mon, 14 May 2007 13:02:42 -0700
Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Andrew Morton wrote:
> > Does "that" have name? I can find no patch in -mm which appears to have
> > anything to do with SMP consolidation, and this patch applies cleanly to
> > the current -mm lineup.
> >
> Sorry, I thought you'd picked this up:
>
>
> Subject: i386: move common parts of smp into their own file
>
> Several parts of kernel/smp.c and smpboot.c are generally useful for
> other subarchitectures and paravirt_ops implementations, so make them
> available for reuse.
Confused. This patch conflicts a lot with James's one (which I named
voyager-fix-build-broken-by-shift-to-smp_ops.patch).
If your "i386: move common parts of smp into their own file" also fixes
Voyager and is preferred then cool, but a) the changelog should tell us
that and b) could James please test it?
next prev parent reply other threads:[~2007-05-14 20:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 16:08 [VOYAGER] fix build broken by shift to smp_ops James Bottomley
2007-05-14 17:10 ` Jeremy Fitzhardinge
2007-05-14 17:22 ` James Bottomley
2007-05-14 19:03 ` Jeremy Fitzhardinge
2007-05-14 20:09 ` Andi Kleen
2007-05-14 19:59 ` Andrew Morton
2007-05-14 20:02 ` Jeremy Fitzhardinge
2007-05-14 20:37 ` Andrew Morton [this message]
2007-05-14 20:48 ` Jeremy Fitzhardinge
2007-05-14 20:54 ` James Bottomley
2007-05-14 21:05 ` Andrew Morton
2007-05-14 21:08 ` James Bottomley
2007-05-14 21:10 ` Jeremy Fitzhardinge
2007-05-14 21:51 ` Andrew Morton
2007-05-14 22:00 ` Jeremy Fitzhardinge
2007-05-14 22:27 ` James Bottomley
2007-05-14 22:55 ` Jeremy Fitzhardinge
2007-05-14 21:58 ` Andi Kleen
2007-05-14 22:29 ` Andrew Morton
2007-05-14 22:40 ` Jeremy Fitzhardinge
2007-05-14 22:42 ` James Bottomley
2007-05-14 22:57 ` Jeremy Fitzhardinge
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=20070514133745.5bfc34ac.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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