From: Eric Biggers <ebiggers@kernel.org>
To: linux-fsdevel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 0/4] vfs: update ->get_link() related documentation
Date: Mon, 22 Apr 2019 11:03:47 -0700 [thread overview]
Message-ID: <20190422180346.GA22674@gmail.com> (raw)
In-Reply-To: <20190411231630.50177-1-ebiggers@kernel.org>
On Thu, Apr 11, 2019 at 04:16:26PM -0700, Eric Biggers wrote:
> Update the documentation as per the discussion at
> https://marc.info/?t=155485312800001&r=1.
>
> Eric Biggers (4):
> Documentation/filesystems/vfs.txt: remove bogus "Last updated" date
> Documentation/filesystems/vfs.txt: document how ->i_link works
> Documentation/filesystems/Locking: fix ->get_link() prototype
> libfs: document simple_get_link()
>
> Documentation/filesystems/Locking | 2 +-
> Documentation/filesystems/vfs.txt | 8 ++++++--
> fs/libfs.c | 14 ++++++++++++++
> 3 files changed, 21 insertions(+), 3 deletions(-)
>
> --
> 2.21.0.392.gf8f6787159e-goog
>
Al, any comment on this? Will you be taking these?
- Eric
next prev parent reply other threads:[~2019-04-22 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 23:16 [PATCH 0/4] vfs: update ->get_link() related documentation Eric Biggers
2019-04-11 23:16 ` [PATCH 1/4] Documentation/filesystems/vfs.txt: remove bogus "Last updated" date Eric Biggers
2019-04-11 23:16 ` [PATCH 2/4] Documentation/filesystems/vfs.txt: document how ->i_link works Eric Biggers
2019-04-11 23:16 ` [PATCH 3/4] Documentation/filesystems/Locking: fix ->get_link() prototype Eric Biggers
2019-04-11 23:16 ` [PATCH 4/4] libfs: document simple_get_link() Eric Biggers
2019-04-22 18:03 ` Eric Biggers [this message]
2019-05-01 0:25 ` [PATCH 0/4] vfs: update ->get_link() related documentation Eric Biggers
2019-05-01 1:36 ` Al Viro
2019-05-01 1:49 ` Jonathan Corbet
2019-05-01 2:14 ` Al Viro
2019-05-01 2:17 ` Jonathan Corbet
2019-05-01 4:00 ` Al Viro
2019-05-01 4:15 ` Tobin C. Harding
2019-05-03 12:16 ` Jonathan Corbet
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=20190422180346.GA22674@gmail.com \
--to=ebiggers@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.