Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Cc: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>,
	linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] docs: filesystems: vfs: actualize struct super_operations description
Date: Tue, 31 Jan 2023 12:56:17 -0700	[thread overview]
Message-ID: <87bkme4gwu.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230131121608.177250-1-aleksandr.mikhalitsyn@canonical.com>

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.

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

Thanks,

jon

  reply	other threads:[~2023-01-31 19:56 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 [this message]
2023-01-31 21:12   ` Aleksandr Mikhalitsyn
2023-02-02  5:25     ` Eric Biggers
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=87bkme4gwu.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=aleksandr.mikhalitsyn@canonical.com \
    --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