From: Christoph Hellwig <hch@infradead.org>
To: Tao Ma <tm@tao.ma>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH V2 for 3.2] fs/direct-io.c: Calculate fs_count correctly in get_more_blocks.
Date: Wed, 2 Nov 2011 03:36:32 -0400 [thread overview]
Message-ID: <20111102073632.GA17580@infradead.org> (raw)
In-Reply-To: <1320200794-2881-1-git-send-email-tm@tao.ma>
The patch looks good to me, but given that it neither fixes a bug
nor a regression I'd probably call it 3.3 material at this point.
next prev parent reply other threads:[~2011-11-02 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111029105856.GA6479@infradead.org>
[not found] ` <1320045873-3956-1-git-send-email-tm@tao.ma>
[not found] ` <x49wrblav46.fsf@segfault.boston.devel.redhat.com>
2011-11-01 3:31 ` [PATCH for 3.2] fs/direct-io.c: Calculate fs_count correctly in get_more_blocks Tao Ma
2011-11-02 2:26 ` [PATCH V2 " Tao Ma
2011-11-02 7:36 ` Christoph Hellwig [this message]
2011-11-03 3:21 ` Tao Ma
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=20111102073632.GA17580@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tm@tao.ma \
--cc=viro@zeniv.linux.org.uk \
/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