From: Theodore Ts'o <tytso@mit.edu>
To: Tao Ma <tm@tao.ma>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Only call update_backups if necessary in online resize.
Date: Wed, 26 Sep 2012 00:03:49 -0400 [thread overview]
Message-ID: <20120926040349.GG11468@thunk.org> (raw)
In-Reply-To: <50627BA5.60106@tao.ma>
On Wed, Sep 26, 2012 at 11:51:01AM +0800, Tao Ma wrote:
> Why? If it isn't the same as the previous one, it will be updated. If
> it is the same, it don't need to be updated. I don't see what your mean
> here.
Oh, I see; sorry, I was just looking at the patch and not the file
with the changes in context. I thought you were updating the backup
descriptors after modifying the last block group in the meta_bg group,
but that was my confusion.
Yes, your patch looks good and I will apply it, thanks!!
- Ted
next prev parent reply other threads:[~2012-09-26 4:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 15:00 [PATCH] ext4: Only call update_backups if necessary in online resize Tao Ma
2012-09-26 3:39 ` Theodore Ts'o
2012-09-26 3:51 ` Tao Ma
2012-09-26 4:03 ` Theodore Ts'o [this message]
2012-09-26 5:26 ` Kevin Liao
2012-09-26 13:57 ` Theodore Ts'o
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=20120926040349.GG11468@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=tm@tao.ma \
/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 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).