From: Christoph Hellwig <hch@infradead.org>
To: Wanlong Gao <wanlong.gao@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthew Wilcox <matthew@wil.cx>,
Wanlong Gao <gaowanlong@cn.fujitsu.com>
Subject: Re: [PATCH] fs:update the NOTE of the file_operations structure
Date: Mon, 18 Jul 2011 13:27:44 -0400 [thread overview]
Message-ID: <20110718172744.GA15785@infradead.org> (raw)
In-Reply-To: <1311009790-10312-1-git-send-email-wanlong.gao@gmail.com>
> /*
> * NOTE:
> * all file operations except setlease can be called without
> - * the big kernel lock held in all filesystems.
> + * the special spin_lock file_lock_lock held in all filesystems.
> */
> struct file_operations {
> struct module *owner;
I'd just remove the comment entirely.
next prev parent reply other threads:[~2011-07-18 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 17:23 [PATCH] fs:update the NOTE of the file_operations structure Wanlong Gao
2011-07-18 17:27 ` Christoph Hellwig [this message]
2011-07-19 0:36 ` Wanlong Gao
-- strict thread matches above, loose matches on Subject: below --
2011-07-19 1:48 Wanlong Gao
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=20110718172744.GA15785@infradead.org \
--to=hch@infradead.org \
--cc=gaowanlong@cn.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=wanlong.gao@gmail.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).