From: Christoph Hellwig <hch@infradead.org>
To: Rusty Russell <rusty@rustcorp.com.au>
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 01:54:10 +0000 [thread overview]
Message-ID: <20031231015410.A12194@infradead.org> (raw)
In-Reply-To: <20031231013046.23B3B2C079@lists.samba.org>; from rusty@rustcorp.com.au on Wed, Dec 31, 2003 at 12:26:34PM +1100
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..
next prev parent reply other threads:[~2003-12-31 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 1:26 [PATCH 1/2] Make for_each_cpu() Iterator More Friendly Rusty Russell
2003-12-31 1:54 ` Christoph Hellwig [this message]
2003-12-31 4:53 ` 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=20031231015410.A12194@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=rusty@rustcorp.com.au \
--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 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.