public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Morton <akpm@linux-foundation.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 14:10:23 -0700	[thread overview]
Message-ID: <4648D03F.4090407@goop.org> (raw)
In-Reply-To: <20070514140530.8e0491cf.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Mon, 14 May 2007 15:54:18 -0500
> James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
>
>   
>> On Mon, 2007-05-14 at 13:37 -0700, Andrew Morton wrote:
>>     
>>> 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?
>>>       
>> OK, let me try a brief history.  A while ago Eric pointed out that the
>> smp ops patch in -mm would break voyager.  So we worked on (and tested a
>> fix for it).  Part of the fix was the prerequisite patch "i386: move
>> common parts of smp into their own file".  The fix on top of this was
>> called "i386: fix voyager build" which actually fixed the voyager build.
>>
>> I've been nagging Andi for a couple of weeks now to get these two
>> upstream.  Finally he replied that the he wasn't planning on sending the
>> precursor "i386: move common parts of smp into their own file" upstream
>> for 2.6.22.  So I had to do a patch that would fix the voyager build
>> without this ... which is what you have.
>>     
>
> uh, I suspected it was something like that.
>
>   
>> So, you either need the single patch you have, or the other two entitled
>>
>> "i386: move common parts of smp into their own file".
>> "i386: fix voyager build" 
>>     
>
> OK, thanks.  I hereby propose that I send the below
> (voyager-fix-build-broken-by-shift-to-smp_ops.patch) to Linus later today,
> provided it passes local testing.
>
> All those in favour say aye?
>   

OK, but only if you don't want to put "i386: move common parts of smp
into their own file" in front of it, and remove the duplicated code.  I
could send you a third copy if you like.

    J

  parent reply	other threads:[~2007-05-14 21:10 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
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 [this message]
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=4648D03F.4090407@goop.org \
    --to=jeremy@goop.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --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