From: Joe Perches <joe@perches.com>
To: Simon Horman <horms@verge.net.au>
Cc: vgoyal@in.ibm.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
hbabu@us.ibm.com, akpm@linux-foundation.org,
ebiederm@xmission.com
Subject: Re: [PATCH] [275/2many] MAINTAINERS - KDUMP
Date: Tue, 16 Oct 2007 19:45:34 -0700 [thread overview]
Message-ID: <1192589134.9998.93.camel@localhost> (raw)
In-Reply-To: <20071017021902.GB6709@verge.net.au>
On Wed, 2007-10-17 at 11:19 +0900, Simon Horman wrote:
> I take it that these changes got shelved or canned,
> as I still don't seem them in Linus' tree.
I have all the changes kept up-to-date.
I still hope to get some variant into a future release.
> But just for the record, the file lists seem
> to be somewhat sort. I'm not sure exactly what the criteria is, but for
> starters, shouldn't all the architecture specific files that only
> contain kexec or kdump code be in there too?
If one of the maintainers, Vivek Goyal or Haren Myneni, cared
to improve the kdump list of files, I'd happily accept it.
My maintainer entry for kdump is:
KDUMP
P: Vivek Goyal
M: vgoyal@in.ibm.com
P: Haren Myneni
M: hbabu@us.ibm.com
L: kexec@lists.infradead.org
L: linux-kernel@vger.kernel.org
W: http://lse.sourceforge.net/kdump/
S: Maintained
F: Documentation/kdump
and if Eric Biederman wants to improve kexec:
KEXEC
P: Eric Biederman
M: ebiederm@xmission.com
W: http://www.xmission.com/~ebiederm/files/kexec/
L: linux-kernel@vger.kernel.org
L: kexec@lists.infradead.org
S: Maintained
F: include/linux/kexec.h
F: kernel/kexec.c
next prev parent reply other threads:[~2007-10-17 2:46 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 [this message]
2007-10-17 3:38 ` Andrew Morton
2007-10-17 3:48 ` Simon Horman
2007-10-17 4:56 ` Joe Perches
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=1192589134.9998.93.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