From: Greg KH <gregkh@linuxfoundation.org>
To: CaTaTo <vahnenko2003@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed
Date: Fri, 13 Mar 2026 08:08:57 +0100 [thread overview]
Message-ID: <2026031331-overrun-palpitate-71c4@gregkh> (raw)
In-Reply-To: <966898e9-229d-495a-bef1-07ce5d2ad640@gmail.com>
On Thu, Mar 12, 2026 at 09:10:34PM +0300, CaTaTo wrote:
> This is related to https://bugzilla.kernel.org/show_bug.cgi?id=221216, I
> attached changed file, sorry again for this is not actual git patch, I made
> this off repo as an quick test fix, I tried make patch from diff, but it
> wouldn't apply for some reason. I added 2 lines on 596 and 597.
That's odd, did you take a look at the documentation for how to make a
patch? Take a look at Documentation/process/submitting-patches.rst
thanks,
greg k-h
next prev parent reply other threads:[~2026-03-13 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 18:10 ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed CaTaTo
2026-03-13 7:08 ` Greg KH [this message]
2026-03-13 9:54 ` CaTaTo
2026-03-13 10:11 ` Greg KH
2026-03-13 11:01 ` Vyacheslav Vahnenko
2026-03-13 12:04 ` Greg KH
2026-03-13 12:36 ` ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed Vyacheslav Vahnenko
2026-03-13 17:20 ` Greg KH
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=2026031331-overrun-palpitate-71c4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=vahnenko2003@gmail.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