From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Ganesan Ramalingam <ganesanr@broadcom.com>,
John Crispin <blogic@openwrt.org>,
Aditya Srivastava <yashsri421@gmail.com>,
linux-mips@vger.kernel.org
Subject: Re: [PATCH] mips: netlogic: fix kernel-doc complaints in fmn-config.c
Date: Thu, 22 Jul 2021 12:07:44 +0200 [thread overview]
Message-ID: <20210722100743.GB7340@alpha.franken.de> (raw)
In-Reply-To: <20210720043432.1684-1-rdunlap@infradead.org>
On Mon, Jul 19, 2021 at 09:34:32PM -0700, Randy Dunlap wrote:
> Clean up kernel-doc warnings in netlogic/xlr/fmn-config.c by using
> correct kernel-doc format. Fixes these warnings:
>
> arch/mips/netlogic/xlr/fmn-config.c:106: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
> * Configure bucket size and credits for a device. 'size' is the size of
> arch/mips/netlogic/xlr/fmn-config.c:181: warning: expecting prototype for Setup the FMN details for each devices according to the device available(). Prototype was for xlr_board_info_setup() instead
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Ganesan Ramalingam <ganesanr@broadcom.com>
> Cc: John Crispin <blogic@openwrt.org>
> Cc: Aditya Srivastava <yashsri421@gmail.com>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: linux-mips@vger.kernel.org
> ---
> arch/mips/netlogic/xlr/fmn-config.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-07-22 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 4:34 [PATCH] mips: netlogic: fix kernel-doc complaints in fmn-config.c Randy Dunlap
2021-07-22 10:07 ` Thomas Bogendoerfer [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=20210722100743.GB7340@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=blogic@openwrt.org \
--cc=ganesanr@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--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).