openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Randy Dunlap" <rdunlap@infradead.org>
Cc: kbuild test robot <lkp@intel.com>,
	linux-aspeed@lists.ozlabs.org,
	Aditya Srivastava <yashsri421@gmail.com>,
	openbmc@lists.ozlabs.org, linux-gpio@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] pinctrl: aspeed: placate kernel-doc warnings
Date: Fri, 23 Jul 2021 13:23:46 +0930	[thread overview]
Message-ID: <d6beadd3-cd57-40ec-aee7-0dc9d8209461@www.fastmail.com> (raw)
In-Reply-To: <20210723034840.8752-1-rdunlap@infradead.org>



On Fri, 23 Jul 2021, at 13:18, Randy Dunlap wrote:
> Eliminate kernel-doc warnings in drivers/pinctrl/aspeed by using
> proper kernel-doc notation.
> 
> Fixes these kernel-doc warnings:
> 
> drivers/pinctrl/aspeed/pinmux-aspeed.c:61: warning: This comment starts 
> with '/**', but isn't a kernel-doc comment. Refer 
> Documentation/doc-guide/kernel-doc.rst
>     * Query the enabled or disabled state for a mux function's signal 
> on a pin
> drivers/pinctrl/aspeed/pinctrl-aspeed.c:135: warning: This comment 
> starts with '/**', but isn't a kernel-doc comment. Refer 
> Documentation/doc-guide/kernel-doc.rst
>     * Search for the signal expression needed to enable the pin's 
> signal for the
> 

Acked-by: Andrew Jeffery <andrew@aj.id.au>

  reply	other threads:[~2021-07-23  3:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23  3:48 [PATCH] pinctrl: aspeed: placate kernel-doc warnings Randy Dunlap
2021-07-23  3:53 ` Andrew Jeffery [this message]
2021-08-10 13:30 ` Linus Walleij

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=d6beadd3-cd57-40ec-aee7-0dc9d8209461@www.fastmail.com \
    --to=andrew@aj.id.au \
    --cc=linus.walleij@linaro.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=rdunlap@infradead.org \
    --cc=yashsri421@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;
as well as URLs for NNTP newsgroup(s).