From: Harvey Harrison <harvey.harrison@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: sct@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH-resend] jbd/jbd2: sparse warnings in revoke.c, journal.c
Date: Wed, 13 Feb 2008 16:55:56 -0800 [thread overview]
Message-ID: <1202950564.18204.37.camel@brick> (raw)
In-Reply-To: <20080213165041.05955133.akpm@linux-foundation.org>
On Wed, 2008-02-13 at 16:50 -0800, Andrew Morton wrote:
> On Wed, 13 Feb 2008 16:33:37 -0800
> Harvey Harrison <harvey.harrison@gmail.com> wrote:
>
> > Subject: [PATCH-resend] jbd/jbd2: sparse warnings in revoke.c, journal.c
>
> ext3/jbd and ext4/jbd2 patches usually find their way into the tree
> via different routes, so bundling these two fixes was inappropriate.
>
> General guidelines: one patch per subsystem and one patch per concept.
>
> Sometimes those guidelines get bent, but only occasionally. Usually
> to avoid the silliness of handling a huge stream of one-line patches.
Sorry, should have known better. Do you want a resend separately?
Harvey
prev parent reply other threads:[~2008-02-14 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 0:33 [PATCH-resend] jbd/jbd2: sparse warnings in revoke.c, journal.c Harvey Harrison
2008-02-14 0:50 ` Andrew Morton
2008-02-14 0:55 ` Harvey Harrison [this message]
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=1202950564.18204.37.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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.