From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Marek Vasut <marek.vasut@mailbox.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: "Tejas Narendra Joglekar" <Tejas.Joglekar@synopsys.com>,
"u-boot@lists.u-boot-project.org"
<u-boot@lists.u-boot-project.org>,
"Patrice Chotard" <patrice.chotard@foss.st.com>,
"Tom Rini" <trini@konsulko.com>,
"Łukasz Majewski" <lukma@nabladev.com>,
"Dan Tran" <Dan.Tran1@synopsys.com>
Subject: Re: [PATCH v3 1/2] usb: gadget: mass_storage: add SuperSpeed descriptor support
Date: Wed, 09 Sep 2026 11:08:47 +0200 [thread overview]
Message-ID: <87zexq6bc0.fsf@kernel.org> (raw)
In-Reply-To: <f5107afa-7202-4116-b02d-29accb4d7617@mailbox.org>
On Wed, Sep 09, 2026 at 04:20, Marek Vasut <marek.vasut@mailbox.org> wrote:
> Hello Thinh,
>
> On 9/9/26 3:58 AM, Thinh Nguyen wrote:
>> On Fri, Sep 04, 2026, Marek Vasut wrote:
>>> On 9/4/26 4:29 AM, Thinh Nguyen wrote:
>>>
>>> Hello Thinh,
>>>
>>>> @@ -2709,6 +2712,27 @@ static int fsg_bind(struct usb_configuration *c, struct usb_function *f)
>>>> return -ENOMEM;
>>>> }
>>>> }
>>>> +
>>>> + if (gadget_is_superspeed(gadget)) {
>>>
>>> Nitpick -- you could invert the conditional here and reduce indent:
>>>
>>> if (!gadget_is_superspeed(gadget))
>>> return 0;
>>>
>>> ...
>>>
>>
>> But wouldn't that deviate further from the original Linux
>> change? See:
>>
>> 4bb99b7c82ba ("usb: gadget: storage: add superspeed support")
>
> I think we are past that point and the U-Boot code did already diverge
> quite a bit, but if this is pulled from some specific Linux commit and
> you want to retain the code similarity, then please at least include the
> aforementioned Linux commit reference in the commit message.
I've been (over-)zealous with keeping the code similar to the Linux
commit.
Sorry if that was a problem.
To me it looks good this way.
>
> 'From Linux 4bb99b7c82ba ("usb: gadget: storage: add superspeed
> support").' or something along these lines.
I can add that to the commit message when applying.
>
> Thank you !
>
> --
> Best regards,
> Marek Vasut
next prev parent reply other threads:[~2026-09-09 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 2:29 [PATCH v3 0/2] usb: gadget: add SuperSpeed descriptor support Thinh Nguyen
2026-09-04 2:29 ` [PATCH v3 1/2] usb: gadget: mass_storage: " Thinh Nguyen
2026-09-04 2:43 ` Marek Vasut
2026-09-09 1:58 ` Thinh Nguyen
2026-09-09 2:20 ` Marek Vasut
2026-09-09 9:08 ` Mattijs Korpershoek [this message]
2026-09-09 13:25 ` Marek Vasut
2026-09-09 9:10 ` Mattijs Korpershoek
2026-09-04 2:29 ` [PATCH v3 2/2] usb: gadget: dfu: " Thinh Nguyen
2026-09-09 9:10 ` Mattijs Korpershoek
2026-09-11 9:25 ` [PATCH v3 0/2] usb: gadget: " Mattijs Korpershoek
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=87zexq6bc0.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=Dan.Tran1@synopsys.com \
--cc=Tejas.Joglekar@synopsys.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=lukma@nabladev.com \
--cc=marek.vasut@mailbox.org \
--cc=patrice.chotard@foss.st.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.