From: Christoph Hellwig <hch@infradead.org>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: viro <viro@zeniv.linux.org.uk>,
Chris Mason <chris.mason@oracle.com>, Ito <t-itoh@jp.fujitsu.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
Linux Fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/2] vfs: make writeback_in_progress() inline
Date: Tue, 6 Dec 2011 04:55:02 -0500 [thread overview]
Message-ID: <20111206095502.GA9138@infradead.org> (raw)
In-Reply-To: <4EDDA9B1.5050000@cn.fujitsu.com>
On Tue, Dec 06, 2011 at 01:35:45PM +0800, Miao Xie wrote:
> writeback_in_progress() is very simple, and we will use writeback_in_progress()
> in the module, so make it inline.
Modules don't really have a business looking at this information. I'd
prefer to keep it static in fs-writeback.c.
prev parent reply other threads:[~2011-12-06 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 5:35 [PATCH 1/2] vfs: make writeback_in_progress() inline Miao Xie
2011-12-06 5:51 ` Miao Xie
2011-12-06 9:55 ` Christoph Hellwig [this message]
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=20111206095502.GA9138@infradead.org \
--to=hch@infradead.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=t-itoh@jp.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).