From: Simon Horman <horms@verge.net.au>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
SH-Linux <linux-sh@vger.kernel.org>
Subject: Re: [PATCH] ARM: shmobile: Remove redundant cpu_disable implementation
Date: Sat, 14 Feb 2015 13:21:38 -0500 [thread overview]
Message-ID: <20150214182133.GA27815@verge.net.au> (raw)
In-Reply-To: <CANqRtoRBpf6gmqUb1avYFWV0sJ5Oo_ZcymRZoDKtm7sgS-zBhA@mail.gmail.com>
On Sat, Feb 14, 2015 at 09:58:42AM +0000, Magnus Damm wrote:
> Hi Stephen,
>
> On Sat, Feb 14, 2015 at 12:41 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> > By default only the non-boot CPUs can be hotplugged if the
> > smp_operations structure doesn't have the cpu_disable function
> > pointer set. r8a7779_cpu_disable() implements the same logic,
> > only non-boot CPUs can be hotplugged, so it's redundant to
> > override the default behavior.
> >
> > Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> > ---
> > arch/arm/mach-shmobile/smp-r8a7779.c | 7 -------
> > 1 file changed, 7 deletions(-)
>
> Thanks for breaking out this change. It looks good to me!
>
> Acked-by: Magnus Damm <damm+renesas@opensource.se>
Thanks,
I have queued this up with the following slightly updated subject
'ARM: shmobile: r8a7779: Remove redundant cpu_disable implementation'
prev parent reply other threads:[~2015-02-14 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 0:41 [PATCH] ARM: shmobile: Remove redundant cpu_disable implementation Stephen Boyd
2015-02-14 9:58 ` Magnus Damm
2015-02-14 18:21 ` Simon Horman [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=20150214182133.GA27815@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sboyd@codeaurora.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