From: Bradley Morgan <include@grrlz.net>
To: akpm@linux-foundation.org
Cc: baoquan.he@linux.dev, pmladek@suse.com,
feng.tang@linux.alibaba.com, gregkh@linuxfoundation.org,
arnd@arndb.de, corbet@lwn.net, rdunlap@infradead.org,
gpiccoli@igalia.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, include@grrlz.net
Subject: [RFC PATCH 4/4] MAINTAINERS: add an entry for the pre kdump notifier list
Date: Sat, 11 Jul 2026 00:22:53 +0000 [thread overview]
Message-ID: <20260711002253.1115-5-include@grrlz.net> (raw)
In-Reply-To: <20260711002253.1115-1-include@grrlz.net>
Scoped to the new file and the header so patches touching the
callback contract get an extra reviewer.
Signed-off-by: Bradley Morgan <include@grrlz.net>
---
MAINTAINERS | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 895a87b571c3..44b6318ed692 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20453,6 +20453,12 @@ L: platform-driver-x86@vger.kernel.org
S: Maintained
F: drivers/platform/x86/panasonic-laptop.c
+PANIC PRE KDUMP NOTIFIER LIST
+M: Bradley Morgan <include@grrlz.net>
+S: Maintained
+F: include/linux/panic_notifier.h
+F: kernel/panic_notifiers.c
+
PARALLAX PING IIO SENSOR DRIVER
M: Andreas Klinger <ak@it-klinger.de>
L: linux-iio@vger.kernel.org
--
2.53.0
prev parent reply other threads:[~2026-07-11 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 0:22 [RFC PATCH 0/4] panic: a pre kdump notifier list for hypervisor upcalls Bradley Morgan
2026-07-11 0:22 ` [RFC PATCH 1/4] panic: add a pre kdump notifier list Bradley Morgan
2026-07-11 0:22 ` [RFC PATCH 2/4] panic: run the pre kdump list before crash kexec Bradley Morgan
2026-07-11 0:22 ` [RFC PATCH 3/4] misc/pvpanic: notify the host on the pre kdump list Bradley Morgan
2026-07-11 0:22 ` Bradley Morgan [this message]
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=20260711002253.1115-5-include@grrlz.net \
--to=include@grrlz.net \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=baoquan.he@linux.dev \
--cc=corbet@lwn.net \
--cc=feng.tang@linux.alibaba.com \
--cc=gpiccoli@igalia.com \
--cc=gregkh@linuxfoundation.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.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