From: Oliver Neukum <oneukum@suse.com>
To: "Linus K." <linus.kaschulla@gmail.com>, linux-usb@vger.kernel.org
Subject: Re: Bug: cdc_acm blocking write after many small writes
Date: Mon, 08 Apr 2019 09:32:36 +0200 [thread overview]
Message-ID: <1554708756.8951.7.camel@suse.com> (raw)
In-Reply-To: <10cfe58c-2d91-30d3-8672-ebe261363bf1@gmail.com>
On Fr, 2019-04-05 at 17:09 +0200, Linus K. wrote:
> Hi,
> I recently submitted this bug to https://bugzilla.kernel.org/ and was
> redirected here.
Hi,
does your kernel have
commit df3aa13c7bbb307e172c37f193f9a7aa058d4739
Author: Oliver Neukum <oneukum@suse.com>
Date: Wed Sep 5 17:56:46 2018 +0200
Revert "cdc-acm: implement put_char() and flush_chars()"
and
commit 93e1c8a638308980309e009cc40b5a57ef87caf1
Author: Romain Izard <romain.izard.pro@gmail.com>
Date: Fri Mar 22 16:53:02 2019 +0100
usb: cdc-acm: fix race during wakeup blocking TX traffic
Regards
Oliver
prev parent reply other threads:[~2019-04-08 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 15:09 Bug: cdc_acm blocking write after many small writes Linus K.
2019-04-08 7:32 ` Oliver Neukum [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=1554708756.8951.7.camel@suse.com \
--to=oneukum@suse.com \
--cc=linus.kaschulla@gmail.com \
--cc=linux-usb@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).