From: Theodore Ts'o <tytso@mit.edu>
To: 文卿 <wenqing.lz@taobao.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: 答复:[ext4:dev 37/40] fs/ext4/extents_status.c:510:22: warning: 'es1' may be used uninitialized in this function
Date: Fri, 1 Feb 2013 12:54:21 -0500 [thread overview]
Message-ID: <20130201175421.GC5228@thunk.org> (raw)
In-Reply-To: <aa4d06e5-f29a-4a98-8a3d-2d80729a993c@taobao.com>
On Fri, Feb 01, 2013 at 01:52:56PM +0800, 文卿 wrote:
> Ted,
> I notice that the patch series of extent status tree has been
> applied into dev branch of ext4. Would you please fix this bug
> directly? I will also fix it in next version. In next version, it
> will contains some other fixes that are suggested by Jan Kara.
Yes, I applied the latest version of your patches into the dev branch
precisely so it could get more testing, including the automated sparse
runs by Wu Fengguang.
I can certainly fix small bugs in the patch series, or if you want to
send me either (a) diffs against what's currently in the dev branch,
or (b) a new patch series, I'll very happily update the dev branch
(the dev branch is one where I will rewind the branch and fix up
commits before pushing to Linus; everything after the master branch is
guaranteed to be cast into concrete, and it's likely that after the
weekend I'll push the master branch to 091e26dfc15.
Cheers,
- Ted
--
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
parent reply other threads:[~2013-02-01 17:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <aa4d06e5-f29a-4a98-8a3d-2d80729a993c@taobao.com>]
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=20130201175421.GC5228@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=wenqing.lz@taobao.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 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).