From: Johan Hovold <johan@kernel.org>
To: Oliver Neukum <oneukum@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan@kernel.org>
Subject: [PATCH 0/2] USB: cdc-acm: fix break reporting
Date: Wed, 29 Sep 2021 11:09:35 +0200 [thread overview]
Message-ID: <20210929090937.7410-1-johan@kernel.org> (raw)
This fixes a couple of bugs in the recently added support for reporting
break events.
Note that the offending commit was backported to stable.
Johan
Johan Hovold (2):
USB: cdc-acm: fix racy tty buffer accesses
USB: cdc-acm: fix break detection
drivers/usb/class/cdc-acm.c | 8 ++++++++
1 file changed, 8 insertions(+)
--
2.32.0
next reply other threads:[~2021-09-29 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 9:09 Johan Hovold [this message]
2021-09-29 9:09 ` [PATCH 1/2] USB: cdc-acm: fix racy tty buffer accesses Johan Hovold
2021-09-30 9:04 ` Oliver Neukum
2021-09-29 9:09 ` [PATCH 2/2] USB: cdc-acm: fix break reporting Johan Hovold
2021-09-30 9:05 ` Oliver Neukum
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=20210929090937.7410-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.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;
as well as URLs for NNTP newsgroup(s).