LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
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:50:41 -0800	[thread overview]
Message-ID: <20080213165041.05955133.akpm@linux-foundation.org> (raw)
In-Reply-To: <1202949217.18204.32.camel@brick>

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.

  reply	other threads:[~2008-02-14  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  0:33 Harvey Harrison
2008-02-14  0:50 ` Andrew Morton [this message]
2008-02-14  0:55   ` Harvey Harrison

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=20080213165041.05955133.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    --subject='Re: [PATCH-resend] jbd/jbd2: sparse warnings in revoke.c, journal.c' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).