From: Greg KH <gregkh@linuxfoundation.org>
To: kushagra765@outlook.com
Cc: linux-doc@vger.kernel.org, corbet@lwn.net, balbi@kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB / dwc3: Fix three doc-build warnings
Date: Sun, 27 Mar 2022 11:52:02 +0200 [thread overview]
Message-ID: <YkAzwtC4Eua92Uag@kroah.com> (raw)
In-Reply-To: <SI2PR01MB3929034AEEE996FA164D94E9F81C9@SI2PR01MB3929.apcprd01.prod.exchangelabs.com>
On Sun, Mar 27, 2022 at 03:05:05PM +0530, kushagra765@outlook.com wrote:
> Two kerneldoc comments in gadget.c have excess function parameter description or wrong
> prototype name and one kerneldoc comment in core.c has a excess function parameter
> description, resulting in these three doc-build warnings:
>
> 1. ./drivers/usb/dwc3/gadget.c:675: warning: Excess function parameter
> 'nfifos' description in 'dwc3_gadget_calc_tx_fifo_size'
> 2. ./drivers/usb/dwc3/gadget.c:700: warning: expecting prototype for
> dwc3_gadget_clear_tx_fifo_size(). Prototype was for dwc3_gadget_clear_tx_fifos()
> instead
> 3. ./drivers/usb/dwc3/core.c:347: warning: Excess function parameter 'ref_clk_per'
> description in 'dwc3_ref_clk_period'
>
> Fix the warnings by correcting the prototype name and removing excess parameter descriptions.
>
> Signed-off-by: Kushagra Verma <kushagra765@outlook.com>
Your "From:" name in your email does not match this name :(
Please fix up and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-27 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 9:35 [PATCH] USB / dwc3: Fix three doc-build warnings kushagra765
2022-03-27 9:52 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-27 10:56 Kushagra Verma
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=YkAzwtC4Eua92Uag@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=corbet@lwn.net \
--cc=kushagra765@outlook.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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