All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.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 12:03:38 -0700	[thread overview]
Message-ID: <4648B28A.5000800@goop.org> (raw)
In-Reply-To: <1179163348.3703.57.camel@mulgrave.il.steeleye.com>

James Bottomley wrote:
> No, I'm proposing this for 2.6.22-rc1 ... Andi has already said he won't
> push the smp consolidation patch for 2.6.22.
>
> Without this patch, voyager won't even build, since the smp_ops broke
> it, so it needs to be fixed *now*.
>   

Sure, I suppose.  But given that the patch which fixes this is a simple
no-functional-changes code-motion patch, it seems odd to not use it in
favour of putting in a big chunk of duplicated code.

    J


  reply	other threads:[~2007-05-14 19:03 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 [this message]
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
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=4648B28A.5000800@goop.org \
    --to=jeremy@goop.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 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.