From: Purva Yeshi <purvayeshi550@gmail.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: "skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc3: Document nostream_work member in dwc3_ep struct
Date: Wed, 12 Feb 2025 19:57:01 +0530 [thread overview]
Message-ID: <85c3ef44-9be6-4264-bfb3-6017c46413c0@gmail.com> (raw)
In-Reply-To: <20250211032002.vhoewlv6bu65m7sl@synopsys.com>
On 11/02/25 08:50, Thinh Nguyen wrote:
> On Thu, Feb 06, 2025, Purva Yeshi wrote:
>> Added description for the 'nostream_work' member in struct dwc3_ep to
>> resolve the kerneldoc warning when running 'make htmldocs'.
>>
>> Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
>> ---
>> drivers/usb/dwc3/core.h | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
>> index ac7c730f8..9095878d7 100644
>> --- a/drivers/usb/dwc3/core.h
>> +++ b/drivers/usb/dwc3/core.h
>> @@ -717,6 +717,7 @@ struct dwc3_event_buffer {
>> /**
>> * struct dwc3_ep - device side endpoint representation
>> * @endpoint: usb endpoint
>> + * @nostream_work: delayed work structure for handling no-stream events
>> * @cancelled_list: list of cancelled requests for this endpoint
>> * @pending_list: list of pending requests for this endpoint
>> * @started_list: list of started requests on this endpoint
>> --
>> 2.34.1
>>
>
> I believe this fix was already added to Greg's usb-linus branch.
>
> BR,
> Thinh
Thank you for the update. I was not aware that this fix had already been
included.
Best regards,
Purva Yeshi
prev parent reply other threads:[~2025-02-12 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 20:27 [PATCH] usb: dwc3: Document nostream_work member in dwc3_ep struct Purva Yeshi
2025-02-11 3:20 ` Thinh Nguyen
2025-02-12 14:27 ` Purva Yeshi [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=85c3ef44-9be6-4264-bfb3-6017c46413c0@gmail.com \
--to=purvayeshi550@gmail.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=skhan@linuxfoundation.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