lkml.org 
[lkml]   [2005]   [Mar]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC/PATCH 0/17][Kdump] Overview
From
Date
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.
>
>
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-04-06 13:31    [W:0.048 / U:0.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site