From: Al Viro <viro@zeniv.linux.org.uk>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 0/4] vfs: update ->get_link() related documentation
Date: Wed, 1 May 2019 02:36:49 +0100 [thread overview]
Message-ID: <20190501013649.GO23075@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20190501002517.GF48973@gmail.com>
On Tue, Apr 30, 2019 at 05:25:17PM -0700, Eric Biggers wrote:
> On Mon, Apr 22, 2019 at 11:03:47AM -0700, Eric Biggers wrote:
> > 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
>
> Ping?
*blink*
Thought I'd replied; apparently not... Anyway, the problem with those
is that there'd been a series of patches converting vfs.txt to new
format; I'm not sure what Jon is going to do with it, but these are
certain to conflict. I've no objections to the contents of changes,
but if that stuff is getting massive reformatting the first two
probably ought to go through Jon's tree. I can take the last two
at any point.
Jon, what's the status of the format conversion?
next prev parent reply other threads:[~2019-05-01 1:36 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 ` [PATCH 0/4] vfs: update ->get_link() related documentation Eric Biggers
2019-05-01 0:25 ` Eric Biggers
2019-05-01 1:36 ` Al Viro [this message]
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=20190501013649.GO23075@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=linux-fsdevel@vger.kernel.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).