From: Lecopzer Chen <lecopzer.chen@mediatek.com>
To: <pmladek@suse.com>
Cc: <acme@kernel.org>, <akpm@linux-foundation.org>,
<alexander.shishkin@linux.intel.com>, <catalin.marinas@arm.com>,
<davem@davemloft.net>, <jolsa@redhat.com>, <jthierry@redhat.com>,
<keescook@chromium.org>, <kernelfans@gmail.com>,
<lecopzer.chen@mediatek.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<linux-perf-users@vger.kernel.org>, <mark.rutland@arm.com>,
<masahiroy@kernel.org>, <matthias.bgg@gmail.com>,
<maz@kernel.org>, <mcgrof@kernel.org>, <mingo@redhat.com>,
<namhyung@kernel.org>, <nixiaoming@huawei.com>,
<peterz@infradead.org>, <sparclinux@vger.kernel.org>,
<sumit.garg@linaro.org>, <wangqing@vivo.com>, <will@kernel.org>,
<yj.chiang@mediatek.com>
Subject: Re: [PATCH 2/5] kernel/watchdog: change watchdog_nmi_enable() to void
Date: Sat, 26 Feb 2022 17:54:52 +0800 [thread overview]
Message-ID: <20220226095452.16924-1-lecopzer.chen@mediatek.com> (raw)
In-Reply-To: <YhjQnMZahzu1w2lj@alley>
> On Sat 2022-02-12 18:43:46, Lecopzer Chen wrote:
> >
> > Nobody cares about the return value of watchdog_nmi_enable(),
> > changing its prototype to void.
> >
> > --- a/arch/sparc/kernel/nmi.c
> > +++ b/arch/sparc/kernel/nmi.c
> > @@ -282,11 +282,11 @@ __setup("nmi_watchdog=", setup_nmi_watchdog);
> > * sparc specific NMI watchdog enable function.
> > * Enables watchdog if it is not enabled already.
> > */
> > -int watchdog_nmi_enable(unsigned int cpu)
> > +void watchdog_nmi_enable(unsigned int cpu)
> > {
> > if (atomic_read(&nmi_active) == -1) {
> > pr_warn("NMI watchdog cannot be enabled or disabled\n");
> > - return -1;
> > + return;
> > }
> >
> > /*
> > @@ -295,11 +295,11 @@ int watchdog_nmi_enable(unsigned int cpu)
> > * process first.
> > */
> > if (!nmi_init_done)
> > - return 0;
> > + return;
> >
> > smp_call_function_single(cpu, start_nmi_watchdog, NULL, 1);
> >
> > - return 0;
> > + return;
>
> Return at the end of the function is superfluous.
Thanks, I'll fix in the next patch.
>
> > }
> > /*
> > * sparc specific NMI watchdog disable function.
>
> Otherwise, it looks good.
>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
>
next prev parent reply other threads:[~2022-02-26 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 10:43 [PATCH 0/5] Support hld based on Pseudo-NMI for arm64 Lecopzer Chen
2022-02-12 10:43 ` [PATCH 1/5] kernel/watchdog: remove WATCHDOG_DEFAULT Lecopzer Chen
2022-02-25 12:47 ` Petr Mladek
2022-02-26 9:52 ` Lecopzer Chen
2022-02-12 10:43 ` [PATCH 2/5] kernel/watchdog: change watchdog_nmi_enable() to void Lecopzer Chen
2022-02-25 12:50 ` Petr Mladek
2022-02-26 9:54 ` Lecopzer Chen [this message]
2022-02-12 10:43 ` [PATCH 3/5] kernel/watchdog_hld: Ensure CPU-bound context when creating hardlockup detector event Lecopzer Chen
2022-02-25 13:15 ` Petr Mladek
2022-02-12 10:43 ` [PATCH 4/5] kernel/watchdog: Adapt the watchdog_hld interface for async model Lecopzer Chen
2022-02-25 15:20 ` Petr Mladek
2022-02-26 10:52 ` Lecopzer Chen
2022-02-28 10:14 ` Petr Mladek
2022-02-28 16:32 ` Lecopzer Chen
2022-02-12 10:43 ` [PATCH 5/5] arm64: Enable perf events based hard lockup detector Lecopzer Chen
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=20220226095452.16924-1-lecopzer.chen@mediatek.com \
--to=lecopzer.chen@mediatek.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=jolsa@redhat.com \
--cc=jthierry@redhat.com \
--cc=keescook@chromium.org \
--cc=kernelfans@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nixiaoming@huawei.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=sparclinux@vger.kernel.org \
--cc=sumit.garg@linaro.org \
--cc=wangqing@vivo.com \
--cc=will@kernel.org \
--cc=yj.chiang@mediatek.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;
as well as URLs for NNTP newsgroup(s).