From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH][ ARM cpu hotplug 1/2 ] extract common code for arm cpu hotplug
Date: Tue, 30 Nov 2010 10:24:11 -0600 [thread overview]
Message-ID: <4CF5252B.5050109@gmail.com> (raw)
In-Reply-To: <20101130110331.GA31054@n2100.arm.linux.org.uk>
On 11/30/2010 05:03 AM, Russell King - ARM Linux wrote:
> On Tue, Nov 30, 2010 at 04:17:32PM +0530, Amit Kucheria wrote:
>> Since the main aim here is to consolidate as much code here as
>> possible while still allowing platforms to override the defaults,
>> would you have an objection to the introduction of a struct smp_ops
>> that'll allow a platform to override the defaults? This seems to be
>> done on other platforms I've briefly looked at.
>
> I see no point to what is being proposed in this thread. It's _soo_
> little code that the platforms have to implement that it really is
> not worth the effort.
>
Whether the code can be consolidated or not, the current API does not
allow a single kernel binary (ignoring the list of other issues). The
introduction of struct smp_ops would help enable both single kernel and
default versions of the functions.
Rob
next prev parent reply other threads:[~2010-11-30 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=fJeOUhH0xUJF8qx-fTJ5popE7ZuVxDZXpTH-i@mail.gmail.com>
2010-11-29 9:54 ` [PATCH][ ARM cpu hotplug 1/2 ] extract common code for arm cpu hotplug Vincent Guittot
2010-11-29 10:41 ` Russell King - ARM Linux
2010-11-29 17:27 ` Vincent Guittot
2010-11-29 19:24 ` Russell King - ARM Linux
2010-11-30 10:47 ` Amit Kucheria
2010-11-30 11:03 ` Russell King - ARM Linux
2010-11-30 11:51 ` Russell King - ARM Linux
2010-11-30 14:05 ` Will Deacon
2010-11-30 16:24 ` Rob Herring [this message]
2010-11-30 16:58 ` Russell King - ARM Linux
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=4CF5252B.5050109@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).