From: Jonathan Corbet <corbet@lwn.net>
To: Sean Anderson <seanga2@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: filesystems: update filesystem locking documentation
Date: Tue, 1 Aug 2017 08:22:38 -0600 [thread overview]
Message-ID: <20170801082238.2e3fa536@lwn.net> (raw)
In-Reply-To: <039038a9-ff79-a6fc-fd98-b0d8abd702d1@gmail.com>
On Tue, 1 Aug 2017 07:09:10 -0400
Sean Anderson <seanga2@gmail.com> wrote:
> Documentation/filesystems/Locking no longer reflects current locking
> semantics. i_mutex is no longer used for locking, and has been superseded
> by i_rwsem. Additionally, ->iterate_shared() was not documented.
>
> Signed-off-by: Sean Anderson <seanga2@gmail.com>
So should I pick this up, or are we waiting for Al to finish
unpacking ... ?
jon
prev parent reply other threads:[~2017-08-01 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 15:53 [PATCH] Documentation: filesystems: update filesystem locking documentation Sean Anderson
2017-07-31 17:23 ` Matthew Wilcox
2017-08-01 11:09 ` [PATCH v2] " Sean Anderson
2017-08-01 11:15 ` Jeff Layton
2017-08-01 14:22 ` Jonathan Corbet [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=20170801082238.2e3fa536@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=seanga2@gmail.com \
--cc=willy@infradead.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).