From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Xu Qiang <xuqiang36@huawei.com>,
pmladek@suse.com, akpm@linux-foundation.org, elver@google.com,
mcgrof@kernel.org, tangmeng@uniontech.com,
yangtiezhu@loongson.cn, john.ogness@linutronix.de,
bigeasy@linutronix.de
Cc: linux-kernel@vger.kernel.org, guohanjun@huawei.com,
weiyongjun1@huawei.com
Subject: Re: [PATCH -next] panic: Add register_panic_notifier and unregister_panic_notifier
Date: Mon, 1 Aug 2022 09:11:46 -0300 [thread overview]
Message-ID: <2d4fa03a-f460-d995-88e8-7f0e58e557bd@igalia.com> (raw)
In-Reply-To: <20220801100509.62282-1-xuqiang36@huawei.com>
On 01/08/2022 07:05, Xu Qiang wrote:
> Add two methods to manipulate panic_notifier_list and export them.
> Subsequently, panic_notifier_list is changed to static variable.
>
> Signed-off-by: Xu Qiang <xuqiang36@huawei.com>
Hi Xu Qiang, first of all, thanks for your patch!
I'd like to mention 2 things about it:
(a) As-is, there's no much use for it - I mean, you're adding a helper
but you didn't change the uses of such notifier list addition (and there
are plenty of them). Are you intend to change it, or just use the new
API in new calls?
(b) Even more important: we are working in a panic notifier refactor
[0], and that'll add new lists. I'm still working on that, plan to
submit (relatively) soon. Maybe worth to wait it, if this one is not urgent?
Cheers,
Guilherme
[0]
https://lore.kernel.org/lkml/20220427224924.592546-1-gpiccoli@igalia.com/
next prev parent reply other threads:[~2022-08-01 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 10:05 Xu Qiang
2022-08-01 12:11 ` Guilherme G. Piccoli [this message]
2022-08-01 13:58 ` xuqiang (M)
2022-08-01 14:25 ` Guilherme G. Piccoli
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=2d4fa03a-f460-d995-88e8-7f0e58e557bd@igalia.com \
--to=gpiccoli@igalia.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=elver@google.com \
--cc=guohanjun@huawei.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=pmladek@suse.com \
--cc=tangmeng@uniontech.com \
--cc=weiyongjun1@huawei.com \
--cc=xuqiang36@huawei.com \
--cc=yangtiezhu@loongson.cn \
/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
all inboxes | Powered by JetHome®