All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@MIT.EDU>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>,
	Andreas Dilger <adilger@sun.com>,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: fix #11321: create /proc/ext4/*/stats et al more carefully
Date: Tue, 9 Sep 2008 14:24:57 -0400	[thread overview]
Message-ID: <20080909182457.GS21071@mit.edu> (raw)
In-Reply-To: <20080909111006.cc8aae89.akpm@linux-foundation.org>

On Tue, Sep 09, 2008 at 11:10:06AM -0700, Andrew Morton wrote:
> 
> "the percpu cleanup patch" is nowhere nearly specific enough to be
> useful.  I don't know what patch this is.

Sorry, I should have been more specific.  It's called:

percpu-counters-clean-up-percpu_counter_sum_and_set-interface.patch 

in in your mmotm tree.

> If stuff turns up in linux-next then I'll just drop the -mm duplicate
> under the assumption that the patch is being taken care of by someone
> else.

Well, in the past you've been asked me not to include non-ext4 patches
in the ext4 tree.  So I could include that patch in an ext4 patchset
and push it to linux-next, since it *does* involve changes to fs/ext4
as well as to include/linux/percpu_counter.h and lib/percpu_counter.c,
if that would be easier.  Or we can keep it out of the set of patches
I push to Linus, but then we have to worry about patch ordering and
dependencies a bit more.

> I will usually attempt to verify that the subsystem tree merged
> the correct patch.  Fairly often they didn't.

I've checked, and modulo some minor changelog comment fixups I had
made to fix grammar and spelling that I had made to my version of the
patch, and the fact that we didn't have your signed-off-by in your
version of the patch, the patch we have is identical.  I'll reconcile
the changelog comments headers on my end, and if you want to keep it
in -mm, I'll send them back to you.  Otherwise I'll include it in ext4
patches and you can drop it from yours if that's OK with you.
Whatever's easier....

							- Ted

  reply	other threads:[~2008-09-09 18:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 21:06 [PATCH] ext4: fix #11321: create /proc/ext4/*/stats et al more carefully Alexey Dobriyan
2008-09-06  7:57 ` Andreas Dilger
2008-09-07 12:15   ` Alexey Dobriyan
2008-09-07 16:04     ` Ralf Hildebrandt
2008-09-07 16:24     ` Theodore Tso
2008-09-07 16:41       ` Alexey Dobriyan
2008-09-08 14:39         ` Theodore Tso
2008-09-09  7:06           ` Alexey Dobriyan
2008-09-09  7:12             ` Andrew Morton
2008-09-09 13:09               ` Theodore Tso
2008-09-09 18:10                 ` Andrew Morton
2008-09-09 18:24                   ` Theodore Tso [this message]
2008-09-09 18:29                     ` Andrew Morton
2008-09-09  7:19           ` Alexey Dobriyan
2008-09-09 11:51 ` Christoph Hellwig

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=20080909182457.GS21071@mit.edu \
    --to=tytso@mit.edu \
    --cc=Ralf.Hildebrandt@charite.de \
    --cc=adilger@sun.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@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 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.