From: Simon Horman <horms@verge.net.au>
To: Joe Perches <joe@perches.com>
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: Wed, 17 Oct 2007 12:48:41 +0900 [thread overview]
Message-ID: <20071017034840.GA28414@verge.net.au> (raw)
In-Reply-To: <1192589134.9998.93.camel@localhost>
On Tue, Oct 16, 2007 at 07:45:34PM -0700, Joe Perches wrote:
> 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.
Understood. I'm happy to make a start on that.
Do you have a criteria for including files.
Are they files that only apply to KEXEC/KDUMP,
or files that have KEXEC/KDUMP code and other code?
> 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
>
>
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
next prev parent reply other threads:[~2007-10-17 3:49 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 [this message]
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=20071017034840.GA28414@verge.net.au \
--to=horms@verge.net.au \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=joe@perches.com \
--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