From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: kexec@lists.infradead.org, vgoyal@in.ibm.com,
linux-kernel@vger.kernel.org, hbabu@us.ibm.com,
Simon Horman <horms@verge.net.au>,
ebiederm@xmission.com, torvalds@linux-foundation.org
Subject: Re: [PATCH] [275/2many] MAINTAINERS - KDUMP
Date: Tue, 16 Oct 2007 20:38:10 -0700 [thread overview]
Message-ID: <20071016203810.00cda8ed.akpm@linux-foundation.org> (raw)
In-Reply-To: <1192589134.9998.93.camel@localhost>
On Tue, 16 Oct 2007 19:45:34 -0700 Joe Perches <joe@perches.com> wrote:
> If one of the maintainers, Vivek Goyal or Haren Myneni, cared
> to improve the kdump list of files, I'd happily accept it.
meh. Bug-reporters only manage to cc the right mailing list 10% of the
time even when it's utterly obvious which subsystem went splat. I wouldn't
worry about fine details such as this.
Anyway, everyone just sends stuff to the great kernel routing service (ie:
me) for the traditional forward-and-ignore treatment.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: Simon Horman <horms@verge.net.au>,
vgoyal@in.ibm.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
hbabu@us.ibm.com, ebiederm@xmission.com
Subject: Re: [PATCH] [275/2many] MAINTAINERS - KDUMP
Date: Tue, 16 Oct 2007 20:38:10 -0700 [thread overview]
Message-ID: <20071016203810.00cda8ed.akpm@linux-foundation.org> (raw)
In-Reply-To: <1192589134.9998.93.camel@localhost>
On Tue, 16 Oct 2007 19:45:34 -0700 Joe Perches <joe@perches.com> wrote:
> If one of the maintainers, Vivek Goyal or Haren Myneni, cared
> to improve the kdump list of files, I'd happily accept it.
meh. Bug-reporters only manage to cc the right mailing list 10% of the
time even when it's utterly obvious which subsystem went splat. I wouldn't
worry about fine details such as this.
Anyway, everyone just sends stuff to the great kernel routing service (ie:
me) for the traditional forward-and-ignore treatment.
next prev parent reply other threads:[~2007-10-17 3:38 UTC|newest]
Thread overview: 14+ 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 ` joe
2007-08-13 6:30 ` [PATCH] [275/2many] MAINTAINERS - KDUMP joe
2007-08-13 6:30 ` joe
2007-10-17 2:19 ` Simon Horman
2007-10-17 2:19 ` Simon Horman
2007-10-17 2:45 ` Joe Perches
2007-10-17 2:45 ` Joe Perches
2007-10-17 3:38 ` Andrew Morton [this message]
2007-10-17 3:38 ` Andrew Morton
2007-10-17 3:48 ` Simon Horman
2007-10-17 3:48 ` Simon Horman
2007-10-17 4:56 ` Joe Perches
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=20071016203810.00cda8ed.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=horms@verge.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.