From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: [GIT PULL] USB driver fixes for 5.10-rc3
Date: Sun, 8 Nov 2020 19:45:49 +0100 [thread overview]
Message-ID: <20201108184549.GA66721@kroah.com> (raw)
The following changes since commit 3cea11cd5e3b00d91caf0b4730194039b45c5891:
Linux 5.10-rc2 (2020-11-01 14:43:51 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git tags/usb-5.10-rc3
for you to fetch changes up to db388a6cb7ed986077d3a275712bfc2e28082760:
Merge tag 'usb-serial-5.10-rc3' of https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial into usb-linus (2020-11-07 15:56:37 +0100)
----------------------------------------------------------------
USB fixes for 5.10-rc3
Here are some small USB fixes and new device ids for 5.10-rc3
They include:
- USB gadget fixes for some reported issues
- Fixes for the every-troublesome apple fastcharge driver,
hopefully we finally have it right.
- More USB core quirks for odd devices
- USB serial driver fixes for some long-standing issues that
were recently found
- some new USB serial driver device ids
All have been in linux-next with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Alan Stern (1):
USB: Add NO_LPM quirk for Kingston flash drive
Daniele Palmas (2):
USB: serial: option: add LE910Cx compositions 0x1203, 0x1230, 0x1231
USB: serial: option: add Telit FN980 composition 0x1055
Evgeny Novikov (1):
usb: gadget: goku_udc: fix potential crashes in probe
Greg Kroah-Hartman (2):
Merge tag 'fixes-for-v5.10-rc2' of git://git.kernel.org/.../balbi/usb into usb-linus
Merge tag 'usb-serial-5.10-rc3' of https://git.kernel.org/.../johan/usb-serial into usb-linus
Heikki Krogerus (1):
usb: dwc3: pci: add support for the Intel Alder Lake-S
Johan Hovold (1):
USB: serial: cyberjack: fix write-URB completion race
Macpaul Lin (1):
usb: mtu3: fix panic in mtu3_gadget_stop()
Martin Blumenstingl (1):
usb: dwc2: Avoid leaving the error_debugfs label unused
Ran Wang (1):
usb: gadget: fsl: fix null pointer checking
Thinh Nguyen (1):
usb: dwc3: ep0: Fix delay status handling
Zhang Qilong (1):
USB: apple-mfi-fastcharge: fix reference leak in apple_mfi_fc_set_property
Ziyi Cao (1):
USB: serial: option: add Quectel EC200T module support
Zqiang (1):
usb: raw-gadget: fix memory leak in gadget_setup
drivers/usb/core/quirks.c | 3 +++
drivers/usb/dwc2/platform.c | 3 +++
drivers/usb/dwc3/dwc3-pci.c | 4 ++++
drivers/usb/dwc3/ep0.c | 3 ++-
drivers/usb/gadget/legacy/raw_gadget.c | 5 ++++-
drivers/usb/gadget/udc/fsl_udc_core.c | 2 +-
drivers/usb/gadget/udc/goku_udc.c | 2 +-
drivers/usb/misc/apple-mfi-fastcharge.c | 4 +++-
drivers/usb/mtu3/mtu3_gadget.c | 1 +
drivers/usb/serial/cyberjack.c | 7 ++++++-
drivers/usb/serial/option.c | 10 ++++++++++
11 files changed, 38 insertions(+), 6 deletions(-)
next reply other threads:[~2020-11-08 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 18:45 Greg KH [this message]
2020-11-08 19:38 ` [GIT PULL] USB driver fixes for 5.10-rc3 pr-tracker-bot
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=20201108184549.GA66721@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=torvalds@linux-foundation.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