From: Christoph Lameter <clameter@sgi.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
arlied@linux.ie, Paul Mackerras <paulus@samba.org>,
rth@twiddle.net, Russell King <rmk@arm.linux.org.uk>,
Tony Luck <tony.luck@intel.com>, Andi Kleen <ak@muc.de>
Subject: Re: [PATCH] Clean up on_each_cpu: should not fail, should not have "retry" arg
Date: Mon, 23 Jul 2007 13:44:09 -0700 [thread overview]
Message-ID: <20070723134409.2174917a@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1184814434.10380.193.camel@localhost.localdomain>
On Thu, 19 Jul 2007 13:07:14 +1000
Rusty Russell <rusty@rustcorp.com.au> wrote:
> Finally, either slub.c's flush_all() can be called with interrupts
> disabled on UP, or the #ifdef is gratuitous. I assumed the latter.
Correct. flush_all() is always called with interrupts disabled. So its
gratuitous.
prev parent reply other threads:[~2007-07-23 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 3:07 [PATCH] Clean up on_each_cpu: should not fail, should not have "retry" arg Rusty Russell
2007-07-23 20:44 ` Christoph Lameter [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=20070723134409.2174917a@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=ak@muc.de \
--cc=arlied@linux.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
--cc=rth@twiddle.net \
--cc=rusty@rustcorp.com.au \
--cc=tony.luck@intel.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