All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: [GIT PULL] USB driver fixes for 4.10-rc5
Date: Sat, 21 Jan 2017 10:29:10 +0100	[thread overview]
Message-ID: <20170121092910.GA29713@kroah.com> (raw)

The following changes since commit 49def1853334396f948dcb4cedb9347abb318df5:

  Linux 4.10-rc4 (2017-01-15 16:21:59 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.10-rc5

for you to fetch changes up to 488dc164914ff5ce5e913abd32048d28fc0d06b8:

  xhci: remove WARN_ON if dma mask is not set for platform devices (2017-01-20 14:55:20 +0100)

----------------------------------------------------------------
USB fixes for 4.10-rc5

Here are a few small USB fixes for 4.10-rc5.

Most of these are gadget/dwc2 fixes for reported issues, all of these
have been in linux-next for a while.  The last one is a single xhci
WARN_ON removal to handle an issue that the dwc3 driver is hitting in
the 4.10-rc tree.  The warning is harmless and needs to be removed, and
a "real" fix that is more complex will show up in 4.11-rc1 for this
device.

That last patch hasn't been in linux-next yet due to the weekend timing,
but it's a "simple" WARN_ON() removal so what could go wrong?  :)

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

----------------------------------------------------------------
Alexandre Belloni (1):
      usb: gadget: udc: atmel: remove memory leak

Amelie Delaunay (1):
      usb: dwc2: gadget: Fix GUSBCFG.USBTRDTIM value

Christophe JAILLET (1):
      usb: gadget: composite: Fix function used to free memory

Greg Kroah-Hartman (1):
      Merge tag 'fixes-for-v4.10-rc5' of git://git.kernel.org/.../balbi/usb into usb-linus

John Stultz (1):
      usb: dwc2: Avoid suspending if we're in gadget mode

Leo Yan (1):
      usb: dwc2: use u32 for DT binding parameters

Mathias Nyman (1):
      xhci: remove WARN_ON if dma mask is not set for platform devices

Nicholas Mc Guire (1):
      usb: dwc2: host: fix Wmaybe-uninitialized warning

Shuah Khan (1):
      usb: dwc3: exynos fix axius clock error path to do cleanup

Vardan Mikayelyan (1):
      usb: dwc2: gadget: Fix DMA memory freeing

Vincent Pelletier (1):
      usb: gadget: f_fs: Fix iterations on endpoints.

 drivers/usb/dwc2/core.h                 |  4 ++--
 drivers/usb/dwc2/gadget.c               | 18 +++++-------------
 drivers/usb/dwc2/hcd.c                  |  7 +++++--
 drivers/usb/dwc2/params.c               | 10 +++++-----
 drivers/usb/dwc3/dwc3-exynos.c          |  4 +++-
 drivers/usb/gadget/composite.c          |  2 +-
 drivers/usb/gadget/function/f_fs.c      | 12 ++++++------
 drivers/usb/gadget/udc/atmel_usba_udc.c |  3 ++-
 drivers/usb/gadget/udc/atmel_usba_udc.h |  1 +
 drivers/usb/host/xhci-plat.c            |  2 +-
 10 files changed, 31 insertions(+), 32 deletions(-)

                 reply	other threads:[~2017-01-21  9:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170121092910.GA29713@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.