mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: akpm@osdl.org, Paul Jackson <pj@sgi.com>,
	anton@samba.org, linux-kernel@vger.kernel.org,
	ioe-lkml@rameria.de, William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [PATCH 1/2] Make for_each_cpu() Iterator More Friendly
Date: Wed, 31 Dec 2003 15:53:36 +1100	[thread overview]
Message-ID: <20031231045528.4E0C22C0CA@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 31 Dec 2003 01:54:10 -0000." <20031231015410.A12194@infradead.org>

In message <20031231015410.A12194@infradead.org> you write:
> On Wed, Dec 31, 2003 at 12:26:34PM +1100, Rusty Russell wrote:
> > Please apply.  Applies against 2.6.0-mm2 and 2.6.0-bk3.  Yay!
> > 
> > Anton: breaks PPC64, as it needs cpu_possible_mask, but fix is already
> > in Ameslab tree.
> 
> So what about including the fix in the patch?  I don't think a fix in some
> obscure tree is a good excuse to break an architecture in a stable series..

Because (1) they've done it already, in anticipation of this change,
and tested it in their tree, and (2) it's a non-trivial patch, as they
don't have a cpu_possible mask concept at all.

FYI, the Ameslab tree is the main PPC64 public tree.

Now, do you need me to explain anything else?
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

      reply	other threads:[~2003-12-31  4:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31  1:26 Rusty Russell
2003-12-31  1:54 ` Christoph Hellwig
2003-12-31  4:53   ` Rusty Russell [this message]

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=20031231045528.4E0C22C0CA@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=hch@infradead.org \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®