All of lore.kernel.org
 help / color / mirror / Atom feed
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.13-rc5
Date: Sat, 5 Jun 2021 12:34:33 +0200	[thread overview]
Message-ID: <YLtTOR0H2AU1QATc@hovoldconsulting.com> (raw)

The following changes since commit f8e8c1b2f782e7391e8a1c25648ce756e2a7d481:

  USB: serial: pl2303: add device id for ADLINK ND-6530 GC (2021-05-10 11:15:23 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git tags/usb-serial-5.13-rc5

for you to fetch changes up to bc96c72df33ee81b24d87eab953c73f7bcc04f29:

  USB: serial: ftdi_sio: add NovaTech OrionMX product ID (2021-06-05 12:26:01 +0200)

----------------------------------------------------------------
USB-serial fixes for 5.13-rc5

Here's a fix for some pipe-direction mismatches in the quatech2 driver,
and a couple of new device ids for ftdi_sio and omninet (and a related
trivial cleanup).

All but the ftdi_sio commit have been in linux-next, and with no
reported issues.

----------------------------------------------------------------
Alexandre GRIVEAUX (2):
      USB: serial: omninet: add device id for Zyxel Omni 56K Plus
      USB: serial: omninet: update driver description

George McCollister (1):
      USB: serial: ftdi_sio: add NovaTech OrionMX product ID

Johan Hovold (1):
      USB: serial: quatech2: fix control-request directions

 drivers/usb/serial/ftdi_sio.c     | 1 +
 drivers/usb/serial/ftdi_sio_ids.h | 1 +
 drivers/usb/serial/omninet.c      | 8 +++++---
 drivers/usb/serial/quatech2.c     | 6 +++---
 4 files changed, 10 insertions(+), 6 deletions(-)

             reply	other threads:[~2021-06-05 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-05 10:34 Johan Hovold [this message]
2021-06-09  8:04 ` [GIT PULL] USB-serial fixes for 5.13-rc5 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=YLtTOR0H2AU1QATc@hovoldconsulting.com \
    --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 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.