archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <>
To: Al Viro <>
Cc: Eric Biggers <>,,
	"Tobin C. Harding" <>
Subject: Re: [PATCH 0/4] vfs: update ->get_link() related documentation
Date: Tue, 30 Apr 2019 20:17:41 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 1 May 2019 03:14:23 +0100
Al Viro <> wrote:

> I do have problems with vfs.txt approach in general and I hope we end up
> with per object type documents; however, that's completely orthogonal to
> format conversion.  IOW, I have no objections whatsoever to format switch
> done first; any migration of e.g. dentry-related parts into a separate
> document, with lifecycle explicitly documented and descriptions of
> methods tied to that can just as well go on top of that.

OK, great.  

That said, let's hold the format conversion for 5.3 (or *maybe*
late-merge-window 5.2).  It's a big set of patches to shovel in at this
point, and while it's good work, it's not screamingly urgent.  My
suggestion would be to take Eric's stuff, it shouldn't be a problem to
adjust to it.

Sound good?



  reply	other threads:[~2019-05-01  2:17 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
2019-05-01  2:14         ` Al Viro
2019-05-01  2:17           ` Jonathan Corbet [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).