From: Vivek Goyal <vgoyal@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
fastboot <fastboot@lists.osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [RFC/PATCH 0/17][Kdump] Overview
Date: Tue, 29 Mar 2005 10:29:13 +0530 [thread overview]
Message-ID: <1112072354.3604.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20050328174827.414a90a9.akpm@osdl.org>
On Mon, 2005-03-28 at 17:48 -0800, Andrew Morton wrote:
> Vivek Goyal <vgoyal@in.ibm.com> wrote:
> >
> > Following patches (as in series file) need to be dropped before applying
> > the fresh ones.
> >
> > crashdump-documentation.patch
> > crashdump-memory-preserving-reboot-using-kexec.patch
> > crashdump-routines-for-copying-dump-pages.patch
> > crashdump-routines-for-copying-dump-pages-fixes.patch
> > crashdump-elf-format-dump-file-access.patch
> > crashdump-linear-raw-format-dump-file-access.patch
> > crashdump-linear-raw-format-dump-file-access-coding-style.patch
>
> At some point we should stop tossing out patches and replacing them in this
> manner.
Andrew, I shall take care of sending incremental patches only next time
onwards. The reason why I did this because changes were relatively large
and I thought dropping the existing series and replacing it with new
series (some patches retaining the old name) might be a better idea.
> Because doing so makes it hard for people to see what has changed.
>
> It makes it hard for people to see that changes in the above patches
> haven't been simply lost.
>
> And the fact that you were probably working against some kernel other than
> -mm gives little confidence that the kdump development team have been
> testing the patches which are presently in -mm. And that is what they are
> there for.
>
>
>
next prev parent reply other threads:[~2005-03-29 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 13:25 Vivek Goyal
2005-03-29 1:48 ` Andrew Morton
2005-03-29 4:59 ` Vivek Goyal [this message]
2005-03-29 7:13 ` [Fastboot] " Suparna Bhattacharya
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=1112072354.3604.14.camel@localhost.localdomain \
--to=vgoyal@in.ibm.com \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome