From: Al Viro <viro@ZenIV.linux.org.uk>
To: LiuQi <liuqi@thunderst.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Steven Liu <lingjiujianke@gmail.com>,
randy.dunlap@oracle.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, dchinner@redhat.com
Subject: Re: [PATCH] code cleanup on fs/super.c
Date: Mon, 21 Mar 2011 04:43:21 +0000 [thread overview]
Message-ID: <20110321044321.GR22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1300680058.3967.11.camel@btg>
On Mon, Mar 21, 2011 at 12:00:58PM +0800, LiuQi wrote:
> and this one?
And this one. Have you actually bothered to read _anything_ in the
thread?
prev parent reply other threads:[~2011-03-21 4:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 8:59 [PATCH] code cleanup on fs/super.c Steven Liu
2011-02-17 16:20 ` Linus Torvalds
2011-02-17 17:25 ` Ted Ts'o
2011-02-17 17:36 ` Al Viro
2011-02-18 2:45 ` Steven Liu
2011-02-18 3:08 ` Al Viro
2011-03-21 4:00 ` LiuQi
2011-03-21 4:43 ` Al Viro [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=20110321044321.GR22723@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dchinner@redhat.com \
--cc=lingjiujianke@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuqi@thunderst.com \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
/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).