From: swarup <swarupkotikalapudi@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>, q@swarup-virtual-machine
Cc: Thinh.Nguyen@synopsys.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] usb: fix kernel-doc warning
Date: Mon, 2 Oct 2023 23:10:06 +0530 [thread overview]
Message-ID: <ZRsAdi/LOEFPY6j1@swarup-virtual-machine> (raw)
In-Reply-To: <2023100207-unmoved-arbitrary-2c33@gregkh>
esOn Mon, Oct 02, 2023 at 05:46:49PM +0200, Greg KH wrote:
> On Mon, Oct 02, 2023 at 09:10:30PM +0530, swarup wrote:
> > On Mon, Oct 02, 2023 at 04:42:03PM +0200, Greg KH wrote:
> > > On Tue, Sep 19, 2023 at 01:05:05AM +0530, Swarup Laxman Kotiaklapudi wrote:
> > > > Fix kernel-doc warnings discovered in usb driver.
> > > > Fixes this warning:
> > > > warning: Function parameter or member 'gfladj_refclk_lpm_sel'
> > > > not described in 'dwc3'
> > > >
> > > > Signed-off-by: Swarup Laxman Kotiaklapudi <swarupkotikalapudi@gmail.com>
> > > > ---
> > > > drivers/usb/dwc3/core.h | 2 ++
> > > > 1 file changed, 2 insertions(+)
> > >
> > > What commit id does this fix?
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > Hi Greg,
> > Please find the commit id as mentioned below,
> > next time onwards i will mention it:
> >
> > Fixes: 5cd07f96c0c6 ("usb: fix kernel-doc warning")
>
> That is not a valid commit id in Linus's tree, are you sure it is
> correct?
>
> And please resend the patch with that information in it.
>
> thanks,
>
> greg k-h
Hi Greg,
I send patch V2, with the Fixes tag being mentioned.
Please check the email.
Thanks,
Swarup
next prev parent reply other threads:[~2023-10-02 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 19:35 [PATCH] usb: fix kernel-doc warning Swarup Laxman Kotiaklapudi
2023-10-02 14:42 ` Greg KH
2023-10-02 15:40 ` swarup
2023-10-02 15:46 ` Greg KH
2023-10-02 17:40 ` swarup [this message]
2023-10-02 17:05 ` [PATCH v2] " Swarup Laxman Kotiaklapudi
2023-10-02 18:26 ` Thinh Nguyen
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=ZRsAdi/LOEFPY6j1@swarup-virtual-machine \
--to=swarupkotikalapudi@gmail.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=q@swarup-virtual-machine \
/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