From: Namhyung Kim <namhyung@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext3: Remove misplaced BUFFER_TRACE() in ext3_truncate()
Date: Mon, 18 Oct 2010 23:53:11 +0900 [thread overview]
Message-ID: <1287413591.1689.25.camel@leonhard> (raw)
In-Reply-To: <4CBC5825.8050502@redhat.com>
2010-10-18 (월), 09:22 -0500, Eric Sandeen:
> As long as you're doing these cleanups, you may as well eyeball ext4
> to see whether the same issues exist; in the case above, it does, and the
> exact same patch (modulo ext3/ext4 changes) applies.
>
> No real point in getting ext3 fixed up and leaving ext4 behind...
>
My plan was sending those patches in a batch after reading ext3 at all.
But it seems to take some time, so now I think that it'd be better to
send them in a small series. I'll prepare it for ext4 (and ext2 too if
you want, Jan) soon. Thanks.
--
Regards,
Namhyung Kim
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Namhyung Kim <namhyung@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext3: Remove misplaced BUFFER_TRACE() in ext3_truncate()
Date: Mon, 18 Oct 2010 23:53:11 +0900 [thread overview]
Message-ID: <1287413591.1689.25.camel@leonhard> (raw)
In-Reply-To: <4CBC5825.8050502@redhat.com>
2010-10-18 (월), 09:22 -0500, Eric Sandeen:
> As long as you're doing these cleanups, you may as well eyeball ext4
> to see whether the same issues exist; in the case above, it does, and the
> exact same patch (modulo ext3/ext4 changes) applies.
>
> No real point in getting ext3 fixed up and leaving ext4 behind...
>
My plan was sending those patches in a batch after reading ext3 at all.
But it seems to take some time, so now I think that it'd be better to
send them in a small series. I'll prepare it for ext4 (and ext2 too if
you want, Jan) soon. Thanks.
--
Regards,
Namhyung Kim
next prev parent reply other threads:[~2010-10-18 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 11:03 [PATCH] ext3: Remove misplaced BUFFER_TRACE() in ext3_truncate() Namhyung Kim
2010-10-18 10:54 ` Jan Kara
2010-10-18 14:22 ` Eric Sandeen
2010-10-18 14:53 ` Namhyung Kim [this message]
2010-10-18 14:53 ` Namhyung Kim
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=1287413591.1689.25.camel@leonhard \
--to=namhyung@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@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.