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 fixes for 6.19-rc6
Date: Fri, 16 Jan 2026 11:19:34 +0100 [thread overview]
Message-ID: <aWoQtivAkG0Dt2pn@hovoldconsulting.com> (raw)
The following changes since commit f8f9c1f4d0c7a64600e2ca312dec824a0bc2f1da:
Linux 6.19-rc3 (2025-12-28 13:24:26 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git tags/usb-serial-6.19-rc6
for you to fetch changes up to cd644b805da8a253198718741bf363c4c58862ff:
USB: serial: f81232: fix incomplete serial port generation (2026-01-13 15:59:07 +0100)
----------------------------------------------------------------
USB serial fix for 6.19-rc6
Here's a fix for an f81232 enumeration issue that could prevent some
ports from being enabled (e.g. during driver rebind).
Included are also some new device ids.
All have been in linux-next with no reported issues.
----------------------------------------------------------------
Ethan Nelson-Moore (1):
USB: serial: ftdi_sio: add support for PICAXE AXE027 cable
Ji-Ze Hong (Peter Hong) (1):
USB: serial: f81232: fix incomplete serial port generation
Ulrich Mohr (1):
USB: serial: option: add Telit LE910 MBIM composition
drivers/usb/serial/f81232.c | 77 ++++++++++++++++++++++++---------------
drivers/usb/serial/ftdi_sio.c | 1 +
drivers/usb/serial/ftdi_sio_ids.h | 2 +
drivers/usb/serial/option.c | 1 +
4 files changed, 51 insertions(+), 30 deletions(-)
next reply other threads:[~2026-01-16 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 10:19 Johan Hovold [this message]
2026-01-16 10:58 ` [GIT PULL] USB serial fixes for 6.19-rc6 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=aWoQtivAkG0Dt2pn@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