Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
To: Albert Ou <aou@eecs.berkeley.edu>,
	 Alexander Gordeev <agordeev@linux.ibm.com>,
	 Andrew Morton <akpm@linux-foundation.org>,
	 Baoquan He <baoquan.he@linux.dev>,
	Borislav Petkov <bp@alien8.de>,
	 Catalin Marinas <catalin.marinas@arm.com>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	 Geert Uytterhoeven <geert@linux-m68k.org>,
	 Heiko Carstens <hca@linux.ibm.com>, Helge Deller <deller@gmx.de>,
	 Huacai Chen <chenhuacai@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	 "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	 Madhavan Srinivasan <maddy@linux.ibm.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	 Pasha Tatashin <pasha.tatashin@soleen.com>,
	Paul Walmsley <pjw@kernel.org>,
	 Pratyush Yadav <pratyush@kernel.org>,
	Rich Felker <dalias@libc.org>,
	 Russell King <linux@armlinux.org.uk>,
	 Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	 Thomas Gleixner <tglx@kernel.org>,
	Vasily Gorbik <gor@linux.ibm.com>,  Will Deacon <will@kernel.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	 x86@kernel.org
Cc: Alexandre Ghiti <alex@ghiti.fr>,
	 Christian Borntraeger <borntraeger@linux.ibm.com>,
	 "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	 Cong Wang <cwang@multikernel.io>,
	Mark Rutland <mark.rutland@arm.com>,
	 Michael Ellerman <mpe@ellerman.id.au>,
	Mike Rapoport <rppt@kernel.org>,
	 Nicholas Piggin <npiggin@gmail.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	 "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
	 Shrikanth Hegde <sshegde@linux.ibm.com>,
	 Sven Schnelle <svens@linux.ibm.com>,
	WANG Xuerui <kernel@xen0n.name>,
	 kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
	 linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
	 linux-mips@vger.kernel.org, linux-parisc@vger.kernel.org,
	 linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org,
	 linux-sh@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	 loongarch@lists.linux.dev
Subject: [PATCH 1/2] MAINTAINERS: add kernel/Kconfig.kexec to KEXEC
Date: Thu, 19 Nov 2026 08:16:57 +0200	[thread overview]
Message-ID: <20261119-arch-kconfig-v1-1-37c276fe4d26@kernel.org> (raw)
In-Reply-To: <20261119-arch-kconfig-v1-0-37c276fe4d26@kernel.org>

kernel/Kconfig.kexec is not matched by the KEXEC entry, so
get_maintainer.pl does not report kexec maintainers for changes in that
file.

Add it to the KEXEC entry.

Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index d738990161bd0..c61a1f0ad330e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14782,6 +14782,7 @@ W:	http://kernel.org/pub/linux/utils/kernel/kexec/
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git
 F:	include/linux/kexec.h
 F:	include/uapi/linux/kexec.h
+F:	kernel/Kconfig.kexec
 F:	kernel/kexec*
 
 KEXEC HANDOVER (KHO)

-- 
2.53.0


  reply	other threads:[~2026-11-19  6:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  6:16 [PATCH 0/2] arch, kexec: declare kexec and crash capabilities in Kconfig.kexec Mike Rapoport (Microsoft)
2026-11-19  6:16 ` Mike Rapoport (Microsoft) [this message]
2026-11-19  7:41   ` [PATCH 1/2] MAINTAINERS: add kernel/Kconfig.kexec to KEXEC Baoquan He
2026-11-19  6:16 ` [PATCH 2/2] arch, kexec: declare kexec and crash capabilities in Kconfig.kexec Mike Rapoport (Microsoft)
2026-11-19  7:29   ` Geert Uytterhoeven
2026-11-19  8:03   ` Heiko Carstens
2026-11-19 11:01   ` Pratyush Yadav

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=20261119-arch-kconfig-v1-1-37c276fe4d26@kernel.org \
    --to=rppt@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=baoquan.he@linux.dev \
    --cc=borntraeger@linux.ibm.com \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=chenhuacai@kernel.org \
    --cc=chleroy@kernel.org \
    --cc=cwang@multikernel.io \
    --cc=dalias@libc.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=deller@gmx.de \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hpa@zytor.com \
    --cc=kernel@xen0n.name \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=loongarch@lists.linux.dev \
    --cc=maddy@linux.ibm.com \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=pjw@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=ritesh.list@gmail.com \
    --cc=sshegde@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    --cc=tglx@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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