public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, Eric Sandeen <sandeen@redhat.com>,
	David Howells <dhowells@redhat.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] fs_parser: update mount_api doc to match function signature
Date: Tue, 26 Nov 2024 12:26:56 +0100	[thread overview]
Message-ID: <20241126112656.e77b263dvznqcvbf@quack3> (raw)
In-Reply-To: <20241125215021.231758-1-rdunlap@infradead.org>

On Mon 25-11-24 13:50:21, Randy Dunlap wrote:
> Add the missing 'name' parameter to the mount_api documentation for
> fs_validate_description().
> 
> Fixes: 96cafb9ccb15 ("fs_parser: remove fs_parameter_description name field")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Eric Sandeen <sandeen@redhat.com>
> Cc: David Howells <dhowells@redhat.com>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: Christian Brauner <brauner@kernel.org>
> Cc: Jan Kara <jack@suse.cz>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org

Looks good. Feel free to add:

Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> ---
>  Documentation/filesystems/mount_api.rst |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> --- linux-next-20241122.orig/Documentation/filesystems/mount_api.rst
> +++ linux-next-20241122/Documentation/filesystems/mount_api.rst
> @@ -770,7 +770,8 @@ process the parameters it is given.
>  
>     * ::
>  
> -       bool fs_validate_description(const struct fs_parameter_description *desc);
> +       bool fs_validate_description(const char *name,
> +                                    const struct fs_parameter_description *desc);
>  
>       This performs some validation checks on a parameter description.  It
>       returns true if the description is good and false if it is not.  It will
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      parent reply	other threads:[~2024-11-26 11:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 21:50 [PATCH] fs_parser: update mount_api doc to match function signature Randy Dunlap
2024-11-26  9:32 ` Christian Brauner
2024-11-26 11:26 ` Jan Kara [this message]

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=20241126112656.e77b263dvznqcvbf@quack3 \
    --to=jack@suse.cz \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dhowells@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sandeen@redhat.com \
    --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