From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 1/2] [POWERPC] smp_call_function_map should be static
Date: Wed, 02 Jan 2008 07:28:33 +1100 [thread overview]
Message-ID: <1199219313.6751.0.camel@pasglop> (raw)
In-Reply-To: <20071228040836.GA23635@lixom.net>
On Thu, 2007-12-27 at 22:08 -0600, Olof Johansson wrote:
> smp_call_function_map should be static, and for consistency prepend it
> with __ like other local helper functions in the same file.
>
> Signed-off-by: Olof Johansson <olof@lixom.net>
NAK. I want it exported to other arch code, I'll need it in some stuff
that I haven't released yet, like some BookE SMP stuff.
Ben.
next prev parent reply other threads:[~2008-01-01 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 4:08 [PATCH 1/2] [POWERPC] smp_call_function_map should be static Olof Johansson
2007-12-28 4:11 ` [PATCH 2/2] [POWERPC] Make smp_send_stop() handle panic and xmon reboot Olof Johansson
2008-01-01 20:28 ` Benjamin Herrenschmidt [this message]
2008-01-01 21:31 ` [PATCH 1/2] [POWERPC] smp_call_function_map should be static Olof Johansson
2008-01-01 22:48 ` Benjamin Herrenschmidt
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=1199219313.6751.0.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).