public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 fixes for 5.3-rc7
Date: Mon, 2 Sep 2019 17:33:51 +0200	[thread overview]
Message-ID: <20190902153351.GA9779@kroah.com> (raw)

The following changes since commit d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1:

  Linux 5.3-rc5 (2019-08-18 14:31:08 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git tags/usb-5.3-rc7

for you to fetch changes up to 1426bd2c9f7e3126e2678e7469dca9fd9fc6dd3e:

  USB: cdc-wdm: fix race between write and disconnect due to flag abuse (2019-08-28 22:48:38 +0200)

----------------------------------------------------------------
USB fixes for 5.3-rc7

Here are some small USB fixes that have been in linux-next this past
week for 5.3-rc7

They fix the usual xhci, syzbot reports, and other small issues that
have come up last week.

All have been in linux-next with no reported issues.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Colin Ian King (1):
      typec: tcpm: fix a typo in the comparison of pdo_max_voltage

Geert Uytterhoeven (1):
      usb: host: xhci: rcar: Fix typo in compatible string matching

Gustavo A. R. Silva (1):
      usb: udc: lpc32xx: silence fall-through warning

Henk van der Laan (1):
      usb-storage: Add new JMS567 revision to unusual_devs

Kai-Heng Feng (2):
      USB: storage: ums-realtek: Update module parameter description for auto_delink_en
      USB: storage: ums-realtek: Whitelist auto-delink support

Nagarjuna Kristam (1):
      usb: host: xhci-tegra: Set DMA mask correctly

Oliver Neukum (2):
      usbtmc: more sanity checking for packet size
      USB: cdc-wdm: fix race between write and disconnect due to flag abuse

Peter Chen (1):
      usb: chipidea: udc: don't do hardware access if gadget has stopped

Schmid, Carsten (1):
      usb: hcd: use managed device resources

Yoshihiro Shimoda (1):
      usb: host: ohci: fix a race condition between shutdown and irq

 drivers/usb/chipidea/udc.c           | 32 ++++++++++++++++++++++++--------
 drivers/usb/class/cdc-wdm.c          | 16 ++++++++++++----
 drivers/usb/class/usbtmc.c           |  3 +++
 drivers/usb/core/hcd-pci.c           | 30 ++++++++----------------------
 drivers/usb/gadget/udc/lpc32xx_udc.c |  2 +-
 drivers/usb/host/ohci-hcd.c          | 15 ++++++++++++---
 drivers/usb/host/xhci-rcar.c         |  2 +-
 drivers/usb/host/xhci-tegra.c        | 10 ++++++++++
 drivers/usb/storage/realtek_cr.c     | 15 +++++++++------
 drivers/usb/storage/unusual_devs.h   |  2 +-
 drivers/usb/typec/tcpm/tcpm.c        |  2 +-
 11 files changed, 82 insertions(+), 47 deletions(-)

             reply	other threads:[~2019-09-02 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 15:33 Greg KH [this message]
2019-09-02 17:05 ` [GIT PULL] USB fixes for 5.3-rc7 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=20190902153351.GA9779@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