From: Daniel Baluta <daniel.baluta@oss.nxp.com>
To: Xu Yang <xu.yang_2@nxp.com>,
Thinh.Nguyen@synopsys.com, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] usb: dwc3: fix a kernel-doc issue
Date: Wed, 4 Mar 2026 14:00:13 +0200 [thread overview]
Message-ID: <f080114c-e13c-4253-9f04-baf148a22d57@oss.nxp.com> (raw)
In-Reply-To: <20260304113916.856841-1-xu.yang_2@nxp.com>
On 3/4/26 13:39, Xu Yang wrote:
> Add '*' to needs_full_reinit comment line to fix a kernel-doc issue.
>
> Fixes: a717321ad7c4 ("usb: dwc3: add needs_full_reinit flag")
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
>
Reviewed-by: Daniel Baluta <daniel.baluta@nxp.com>
next prev parent reply other threads:[~2026-03-04 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 11:39 [PATCH v2 1/2] usb: dwc3: fix a kernel-doc issue Xu Yang
2026-03-04 11:39 ` [PATCH v2 2/2] usb: dwc3: fix a typo 'HishSpeed' Xu Yang
2026-03-04 11:59 ` Daniel Baluta
2026-03-05 1:34 ` Thinh Nguyen
2026-03-04 12:00 ` Daniel Baluta [this message]
2026-03-05 1:33 ` [PATCH v2 1/2] usb: dwc3: fix a kernel-doc issue 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=f080114c-e13c-4253-9f04-baf148a22d57@oss.nxp.com \
--to=daniel.baluta@oss.nxp.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=xu.yang_2@nxp.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