public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Anup K Parikh <parikhanupk.foss@gmail.com>
Cc: linux-kernel@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] Doc fix for dget_dlock
Date: Tue, 9 Aug 2022 09:29:42 -0600	[thread overview]
Message-ID: <a7d3882f-5a70-e168-14f5-14795cff8119@linuxfoundation.org> (raw)
In-Reply-To: <Yu1HwVoTYOeaCh4v@autolfshost>

On 8/5/22 10:39 AM, Anup K Parikh wrote:
> Removes the warning for dget_dlock in include/linux/dcache.h and
> enables generation of its API documentation
> 
> Signed-off-by: Anup K Parikh <parikhanupk.foss@gmail.com>
> ---
>   include/linux/dcache.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/dcache.h b/include/linux/dcache.h
> index f5bba5148..ce0b36f72 100644
> --- a/include/linux/dcache.h
> +++ b/include/linux/dcache.h
> @@ -297,7 +297,7 @@ extern char *dentry_path(const struct dentry *, char *, int);
>   /* Allocation counts.. */
>   
>   /**
> - *	dget, dget_dlock -	get a reference to a dentry
> + *	dget_dlock -	get a reference to a dentry
>    *	@dentry: dentry to get a reference to
>    *
>    *	Given a dentry or %NULL pointer increment the reference count
> 

Please include all the maintainers - run get_maintainers.pl for a
complete list.

thanks,
-- Shuah

  reply	other threads:[~2022-08-09 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 16:39 [PATCH] Doc fix for dget_dlock Anup K Parikh
2022-08-09 15:29 ` Shuah Khan [this message]
2022-08-09 18:28 ` Randy Dunlap
     [not found]   ` <CAH6MFJGuHptQ8peBb8myLR8fgtLtAXwvUePcs7dbzYszF9Yyyw@mail.gmail.com>
2022-08-11 18:33     ` Randy Dunlap
2022-08-11 18:35       ` Randy Dunlap

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=a7d3882f-5a70-e168-14f5-14795cff8119@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parikhanupk.foss@gmail.com \
    /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