From: Xiaoming Ni <nixiaoming@huawei.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Pavel Machek <pavel@ucw.cz>
Cc: <linux-kernel@vger.kernel.org>, <linux-leds@vger.kernel.org>,
<dmurphy@ti.com>, <akpm@linux-foundation.org>,
<keescook@chromium.org>, <gpiccoli@canonical.com>,
<wangle6@huawei.com>
Subject: Re: [PATCH 2/4] hung_task: Replace "did_panic" with is_be_panic()
Date: Sun, 20 Dec 2020 10:58:44 +0800 [thread overview]
Message-ID: <d5c62a81-2b52-5add-98c9-bb75e9b2f436@huawei.com> (raw)
In-Reply-To: <a2279e36-3665-6328-e515-b12cdc532aa9@infradead.org>
On 2020/12/19 1:06, Randy Dunlap wrote:
> On 12/18/20 6:36 AM, Tetsuo Handa wrote:
>> On 2020/12/18 21:59, Pavel Machek wrote:
>>> On Fri 2020-12-18 19:44:04, Xiaoming Ni wrote:
>>> Plus.. is_being_panic is not really english. "is_paniccing" would be
>>> closer...?
>>
>> Or in_panic() ?
>>
>
> Yes, or in_panic_state()
>
Thank you,
I'll resend the patch later on according to your suggestion.
Thanks
Xiaoming Ni
.
next prev parent reply other threads:[~2020-12-20 2:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 11:44 [PATCH 0/4] Add new API is_being_panic() Xiaoming Ni
2020-12-18 11:44 ` [PATCH 1/4] 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 [this message]
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=d5c62a81-2b52-5add-98c9-bb75e9b2f436@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=rdunlap@infradead.org \
--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).