From: Eric Biggers <ebiggers@kernel.org>
To: Aleksandr Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] docs: filesystems: vfs: actualize struct super_operations description
Date: Wed, 1 Feb 2023 21:25:18 -0800 [thread overview]
Message-ID: <Y9tJPn0a/O27SBuJ@sol.localdomain> (raw)
In-Reply-To: <CAEivzxfxkWtYP4bqFrmD__3M9WpJNZjTJNx9wp4WQ0_LoGKT6g@mail.gmail.com>
On Tue, Jan 31, 2023 at 10:12:42PM +0100, Aleksandr Mikhalitsyn wrote:
> On Tue, Jan 31, 2023 at 8:56 PM Jonathan Corbet <corbet@lwn.net> wrote:
> >
> > Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com> writes:
> >
> > > Cc: linux-fsdevel@vger.kernel.org
> > > Cc: linux-doc@vger.kernel.org
> > > Signed-off-by: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
> > > ---
> > > Documentation/filesystems/vfs.rst | 74 ++++++++++++++++++++++++-------
> > > 1 file changed, 59 insertions(+), 15 deletions(-)
> >
> > Thanks for updating this document! That said, could I ask you, please,
> > to resubmit these with a proper changelog? I'd also suggest copying Al
> > Viro, who will surely have comments on the changes you have made.
>
> Hi, Jonathan!
>
> Sure. Have done and of course I've to add Al Viro to CC, but forgot to do that,
> cause scripts/get_maintainer.pl have didn't remind me (-:
>
> >
> > > diff --git a/Documentation/filesystems/vfs.rst b/Documentation/filesystems/vfs.rst
> > > index fab3bd702250..8671eafa745a 100644
> > > --- a/Documentation/filesystems/vfs.rst
> > > +++ b/Documentation/filesystems/vfs.rst
> > > @@ -242,33 +242,42 @@ struct super_operations
> > > -----------------------
> > >
> > > This describes how the VFS can manipulate the superblock of your
> > > -filesystem. As of kernel 2.6.22, the following members are defined:
> > > +filesystem. As of kernel 6.1, the following members are defined:
> >
> > Why not 6.2 while you're at it? We might as well be as current as we
> > can while we're updating things.
>
> I'm on 6.2, but for some reason decided to put 6.1. Will fix it :)
>
It would be better to just remove the version number. Whenever documentation
says something like "as of vX.Y.Z", people usually forget to update the version
number when updating the documentation. So then we end up in the situation
where the documentation actually describes the latest kernel version, but it
claims to be describing an extremely old kernel version.
- Eric
next prev parent reply other threads:[~2023-02-02 5:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 12:16 [PATCH 2/2] docs: filesystems: vfs: actualize struct super_operations description Alexander Mikhalitsyn
2023-01-31 19:56 ` Jonathan Corbet
2023-01-31 21:12 ` Aleksandr Mikhalitsyn
2023-02-02 5:25 ` Eric Biggers [this message]
2023-02-02 9:46 ` Aleksandr Mikhalitsyn
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=Y9tJPn0a/O27SBuJ@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.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