From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Mahoney <jeffm@suse.com>
Cc: torvalds@linux-foundation.org, reiserfs-devel@vger.kernel.org
Subject: Re: [patch 0/7] reiserfs fixes patch set
Date: Wed, 17 Oct 2007 15:11:40 -0700 [thread overview]
Message-ID: <20071017151140.c5b782ef.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071016230210.779927000@suse.com>
On Tue, 16 Oct 2007 19:02:10 -0400
Jeff Mahoney <jeffm@suse.com> wrote:
> This is a series of "safe" patches that have been in the openSUSE kernel
> for a while now.
>
I'm not particularly happy seeing a large number of complex-looking patches
against a not-very-well-maintained important filesystem more than a week
into the merge window. It would have been far better to get this stuff
sent a month ago.
Now we're left with a choice between holding it all back for 2.5 months or
just jamming it into mainline with basically no testing. I sure hope it
got good testing in the suse kernel.
next prev parent reply other threads:[~2007-10-17 22:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 23:02 [patch 0/7] reiserfs fixes patch set Jeff Mahoney
2007-10-16 23:02 ` [patch 1/7] reiserfs: fix up lockdep warnings Jeff Mahoney
2007-10-16 23:02 ` [patch 2/7] reiserfs: dont use BUG when panicking Jeff Mahoney
2007-10-16 23:02 ` [patch 3/7] reiserfs: use is_reusable to catch corruption Jeff Mahoney
2007-10-16 23:02 ` [patch 4/7] reiserfs: fix usage of signed ints for block numbers Jeff Mahoney
2007-10-16 23:02 ` [patch 5/7] reiserfs: fix memset byte count during resize Jeff Mahoney
2007-10-16 23:02 ` [patch 6/7] reiserfs: remove first_zero_hint Jeff Mahoney
2007-10-18 18:02 ` Jeff Mahoney
2007-10-16 23:02 ` [patch 7/7] reiserfs: ignore on disk s_bmap_nr value Jeff Mahoney
2007-10-17 22:19 ` Andrew Morton
2007-10-17 22:11 ` Andrew Morton [this message]
2007-10-17 22:19 ` [patch 0/7] reiserfs fixes patch set Linus Torvalds
2007-10-17 23:23 ` Jeff Mahoney
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=20071017151140.c5b782ef.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jeffm@suse.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.