From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Daniel Axtens <dja@axtens.net>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 1/1] hotplug-cpu.c: show 'last online CPU' error in dlpar_cpu_offline()
Date: Fri, 26 Mar 2021 11:08:01 -0300 [thread overview]
Message-ID: <b9a6e77c-4319-ff08-493f-43e02388701b@gmail.com> (raw)
In-Reply-To: <871rc28p1w.fsf@linkitivity.dja.id.au>
Hey Daniel,
On 3/26/21 2:24 AM, Daniel Axtens wrote:
> Hi Daniel,
>
> Two small nitpicks:
>
>> This patch adds a 'last online' check in dlpar_cpu_offline() to catch
>> the 'last online CPU' offline error, eturning a more informative error
> ^--- s/eturning/returning/;
>
>
>> + /* device_offline() will return -EBUSY (via cpu_down())
>> + * if there is only one CPU left. Check it here to fail
>> + * earlier and with a more informative error message,
>> + * while also retaining the cpu_add_remove_lock to be sure
>> + * that no CPUs are being online/offlined during this
>> + * check. */
>
> Checkpatch has a small issue with this comment:
>
> WARNING: Block comments use a trailing */ on a separate line
> #50: FILE: arch/powerpc/platforms/pseries/hotplug-cpu.c:279:
> + * check. */
>
> Apart from that, this patch seems sane to me, but I haven't been able to
> test it.
Thanks for the review, and for letting me know of the existence of
'scripts/checkpatch.pl' to verify the patches before posting. I'll
send a v3.
Thanks,
DHB
>
> Kind regards,
> Daniel
>
next prev parent reply other threads:[~2021-03-26 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 20:50 [PATCH v2 0/1] show 'last online CPU' error in dlpar_cpu_offline() Daniel Henrique Barboza
2021-03-23 20:50 ` [PATCH v2 1/1] hotplug-cpu.c: " Daniel Henrique Barboza
2021-03-26 5:24 ` Daniel Axtens
2021-03-26 14:08 ` Daniel Henrique Barboza [this message]
2021-03-31 1:09 ` [PATCH v2 0/1] " Michael Ellerman
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=b9a6e77c-4319-ff08-493f-43e02388701b@gmail.com \
--to=danielhb413@gmail.com \
--cc=dja@axtens.net \
--cc=linuxppc-dev@lists.ozlabs.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).