From: Johan Hovold <johan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Subject: [GIT PULL] USB-serial fixes for 5.10-rc7
Date: Fri, 4 Dec 2020 12:14:44 +0100 [thread overview]
Message-ID: <X8oaJPqNvhGB/2Sd@localhost> (raw)
The following changes since commit 09162bc32c880a791c6c0668ce0745cf7958f576:
Linux 5.10-rc4 (2020-11-15 16:44:31 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git tags/usb-serial-5.10-rc7
for you to fetch changes up to 3f203f057edfcf6bd02c6b942799262bfcf31f73:
USB: serial: kl5kusb105: fix memleak on open (2020-12-04 12:02:57 +0100)
----------------------------------------------------------------
USB-serial fixes for 5.10-rc7
Here's a fix for a regression in the option driver which has been
backported to the stable trees and fix for a small memory leak on open
in the kl5kusb105 driver.
Included are also various new device ids.
All but the memleak fix has been in linux-next and with no reported
issues.
----------------------------------------------------------------
Bjørn Mork (1):
USB: serial: option: fix Quectel BG96 matching
Giacinto Cifelli (1):
USB: serial: option: add support for Thales Cinterion EXS82
Jan-Niklas Burfeind (1):
USB: serial: ch341: add new Product ID for CH341A
Johan Hovold (2):
USB: serial: ch341: sort device-id entries
USB: serial: kl5kusb105: fix memleak on open
Vincent Palatin (1):
USB: serial: option: add Fibocom NL668 variants
drivers/usb/serial/ch341.c | 5 +++--
drivers/usb/serial/kl5kusb105.c | 10 ++++------
drivers/usb/serial/option.c | 10 ++++++----
3 files changed, 13 insertions(+), 12 deletions(-)
next reply other threads:[~2020-12-04 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 11:14 Johan Hovold [this message]
2020-12-04 12:27 ` [GIT PULL] USB-serial fixes for 5.10-rc7 Greg Kroah-Hartman
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=X8oaJPqNvhGB/2Sd@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--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