From: Jonathan Corbet <corbet@lwn.net>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Eric Biggers <ebiggers@kernel.org>,
linux-fsdevel@vger.kernel.org,
"Tobin C. Harding" <tobin@kernel.org>
Subject: Re: [PATCH 0/4] vfs: update ->get_link() related documentation
Date: Tue, 30 Apr 2019 19:49:43 -0600 [thread overview]
Message-ID: <20190430194943.4a7916be@lwn.net> (raw)
In-Reply-To: <20190501013649.GO23075@ZenIV.linux.org.uk>
On Wed, 1 May 2019 02:36:49 +0100
Al Viro <viro@zeniv.linux.org.uk> wrote:
> 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?
Last I saw, it seemed that you wanted changes in how things were done and
that Tobin (added to CC) had stepped back. Tobin, are your thoughts on
the matter different? I could try to shoehorn them in for 5.2 still, I
guess, but perhaps the best thing to do is to just take Eric's patch, and
the reformatting can work around it if need be.
Thanks,
jon
next prev parent reply other threads:[~2019-05-01 1:49 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
2019-05-01 1:49 ` Jonathan Corbet [this message]
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=20190430194943.4a7916be@lwn.net \
--to=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tobin@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 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).