From: Joe Perches <joe@perches.com>
To: Simon Horman <horms@verge.net.au>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
hbabu@us.ibm.com, vgoyal@in.ibm.com, ebiederm@xmission.com,
akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] [275/2many] MAINTAINERS - KDUMP
Date: Tue, 16 Oct 2007 21:56:19 -0700 [thread overview]
Message-ID: <1192596979.9998.143.camel@localhost> (raw)
In-Reply-To: <20071017034840.GA28414@verge.net.au>
On Wed, 2007-10-17 at 12:48 +0900, Simon Horman wrote:
> Do you have a criteria for including files.
A file or file pattern specific to a maintained "subsystem".
Any time a subsystem file pattern matches a file,
maintainers would be cc'd. The matching is non-exclusive.
Multiple subsystems can include the same file pattern.
For KDUMP, maybe a file pattern should be:
F: arch/*/kernel/crash_dump.c
F: include/linux/crash_dump.h
> Are they files that only apply to KEXEC/KDUMP,
> or files that have KEXEC/KDUMP code and other code?
I think it should be files specific to KDUMP and not
files shared with other subsystems but perhaps it's
maintainer taste.
If the files patterns are not specific to kdump,
the kdump maintainers will be cc'd on patches that
change files where kdump functions aren't modified.
The list of files that include crash_dump.h is pretty long.
$ grep -P -l -r --include=*.[ch] crash_dump.h *
arch/i386/kernel/crash_dump.c
arch/i386/kernel/setup.c
arch/ia64/hp/common/sba_iommu.c
arch/ia64/kernel/crash.c
arch/ia64/kernel/setup.c
arch/powerpc/kernel/crash.c
arch/powerpc/kernel/crash_dump.c
arch/sh/kernel/crash_dump.c
arch/x86_64/kernel/crash_dump.c
arch/x86_64/kernel/setup.c
drivers/char/mem.c
fs/proc/proc_misc.c
fs/proc/vmcore.c
The list of files that use CONFIG_CRASH_DUMP is also
pretty long and seemingly unrelated.
$ grep -P -l -r --include=*.[ch] CONFIG_CRASH_DUMP *
arch/i386/kernel/apic.c
arch/i386/kernel/e820.c
arch/ia64/hp/common/sba_iommu.c
arch/ia64/kernel/efi.c
arch/powerpc/kernel/iommu.c
arch/powerpc/platforms/cell/ras.c
arch/powerpc/platforms/pseries/iommu.c
arch/x86_64/kernel/e820.c
drivers/char/mem.c
include/asm-powerpc/kdump.h
include/linux/bootmem.h
include/linux/crash_dump.h
mm/bootmem.c
prev parent reply other threads:[~2007-10-17 5:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:30 [PATCH] [281/2many] MAINTAINERS - KEXEC joe
2007-08-13 6:30 ` [PATCH] [275/2many] MAINTAINERS - KDUMP joe
2007-10-17 2:19 ` Simon Horman
2007-10-17 2:45 ` Joe Perches
2007-10-17 3:38 ` Andrew Morton
2007-10-17 3:48 ` Simon Horman
2007-10-17 4:56 ` Joe Perches [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=1192596979.9998.143.camel@localhost \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@in.ibm.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