public inbox for linux-kernel@vger.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, linux-kernel@vger.kernel.org
Subject: [GIT PULL] USB-serial updates for 6.5-rc1
Date: Fri, 23 Jun 2023 09:12:56 +0200	[thread overview]
Message-ID: <ZJVF-Gq2HCkv49sH@hovoldconsulting.com> (raw)

The following changes since commit 9561de3a55bed6bdd44a12820ba81ec416e705a7:

  Linux 6.4-rc5 (2023-06-04 14:04:27 -0400)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git tags/usb-serial-6.5-rc1

for you to fetch changes up to ffa5f7a3bf28c1306eef85d4056539c2d4b8eb09:

  USB: serial: option: add LARA-R6 01B PIDs (2023-06-22 13:45:09 +0200)

----------------------------------------------------------------
USB-serial updates for 6.5-rc1

Here are the USB-serial updates for 6.5-rc1, including:

 - improved error handling for break signalling
 - report to user space when a device does not support break signalling

Included are also some new modem device ids.

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

----------------------------------------------------------------
Davide Tronchin (1):
      USB: serial: option: add LARA-R6 01B PIDs

Johan Hovold (3):
      USB: serial: return errors from break handling
      USB: serial: cp210x: disable break signalling on CP2105 SCI
      USB: serial: report unsupported break signalling

 drivers/usb/serial/ark3116.c          |  7 +++++--
 drivers/usb/serial/belkin_sa.c        | 12 +++++++++---
 drivers/usb/serial/ch341.c            | 37 ++++++++++++++++++++++-------------
 drivers/usb/serial/cp210x.c           | 14 ++++++++++---
 drivers/usb/serial/digi_acceleport.c  |  7 ++++---
 drivers/usb/serial/f81232.c           |  4 +++-
 drivers/usb/serial/f81534.c           |  4 +++-
 drivers/usb/serial/ftdi_sio.c         | 10 +++++++---
 drivers/usb/serial/io_edgeport.c      |  6 ++++--
 drivers/usb/serial/io_ti.c            |  9 +++++++--
 drivers/usb/serial/keyspan.c          |  5 ++++-
 drivers/usb/serial/keyspan_pda.c      |  8 ++++++--
 drivers/usb/serial/mct_u232.c         |  6 +++---
 drivers/usb/serial/mos7720.c          |  9 +++++----
 drivers/usb/serial/mos7840.c          |  7 ++++---
 drivers/usb/serial/mxuport.c          |  6 +++---
 drivers/usb/serial/option.c           |  4 ++++
 drivers/usb/serial/pl2303.c           | 14 ++++++++-----
 drivers/usb/serial/quatech2.c         |  8 ++++++--
 drivers/usb/serial/ti_usb_3410_5052.c | 10 +++++++---
 drivers/usb/serial/upd78f0730.c       |  7 +++++--
 drivers/usb/serial/usb-serial.c       |  4 ++--
 drivers/usb/serial/usb_debug.c        | 13 +++++++++---
 drivers/usb/serial/whiteheat.c        |  7 ++++---
 drivers/usb/serial/xr_serial.c        |  4 ++--
 include/linux/usb/serial.h            |  2 +-
 26 files changed, 151 insertions(+), 73 deletions(-)

             reply	other threads:[~2023-06-23  7:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  7:12 Johan Hovold [this message]
2023-06-23  7:44 ` [GIT PULL] USB-serial updates for 6.5-rc1 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=ZJVF-Gq2HCkv49sH@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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