From: Xiaoming Ni <nixiaoming@huawei.com>
To: <linux-kernel@vger.kernel.org>, <linux-leds@vger.kernel.org>,
<pavel@ucw.cz>, <dmurphy@ti.com>, <akpm@linux-foundation.org>,
<keescook@chromium.org>, <gpiccoli@canonical.com>,
<penguin-kernel@i-love.sakura.ne.jp>
Cc: <nixiaoming@huawei.com>, <wangle6@huawei.com>
Subject: [PATCH 0/4] Add new API is_being_panic()
Date: Fri, 18 Dec 2020 19:44:02 +0800 [thread overview]
Message-ID: <20201218114406.61906-1-nixiaoming@huawei.com> (raw)
Add is_being_panic() to check whether the system is in panic state.
Used to replace the global variable used to determine the panic status
in other features: hung_task ledtrig-activity ledtrig-heartbeat
Xiaoming Ni (4):
panic: Add new API is_being_panic()
hung_task: Replace "did_panic" with is_be_panic()
leds:trigger:ledtrig-activity Replace "panic_detected" with
is_be_panic()
leds:trigger:ledtrig-heartbeat: Replace "panic_heartbeats" with
is_be_panic()
drivers/leds/trigger/ledtrig-activity.c | 19 +------------------
drivers/leds/trigger/ledtrig-heartbeat.c | 19 +------------------
include/linux/kernel.h | 1 +
kernel/hung_task.c | 17 +----------------
kernel/panic.c | 6 ++++++
5 files changed, 10 insertions(+), 52 deletions(-)
--
2.27.0
next reply other threads:[~2020-12-18 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 11:44 Xiaoming Ni [this message]
2020-12-18 11:44 ` [PATCH 1/4] panic: Add new API is_being_panic() Xiaoming Ni
2020-12-18 11:44 ` [PATCH 2/4] hung_task: Replace "did_panic" with is_be_panic() Xiaoming Ni
2020-12-18 12:59 ` Pavel Machek
2020-12-18 14:36 ` Tetsuo Handa
2020-12-18 17:06 ` Randy Dunlap
2020-12-20 2:58 ` Xiaoming Ni
2020-12-18 11:44 ` [PATCH 3/4] leds:trigger:ledtrig-activity Replace "panic_detected" " Xiaoming Ni
2020-12-18 11:44 ` [PATCH 4/4] leds:trigger:ledtrig-heartbeat: Replace "panic_heartbeats" " Xiaoming Ni
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=20201218114406.61906-1-nixiaoming@huawei.com \
--to=nixiaoming@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dmurphy@ti.com \
--cc=gpiccoli@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=wangle6@huawei.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).