Hi Greg,
Here are my exceptionally late usb-serial updates for 4.8-rc1. Mostly
clean ups, so there's nothing here (except the device-id patch) which
cannot wait until 4.9 if you prefer to hold off on these instead of
sending a second pull-request to Linus.
All have been in linux-next without any reported issues.
I still have some backlog of patches pending review that I will get to
in the coming weeks.
Thanks,
Johan
The following changes since commit 92d21ac74a9e3c09b0b01c764e530657e4c85c49:
Linux 4.7-rc7 (2016-07-10 20:24:59 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git tags/usb-serial-4.8-rc1
for you to fetch changes up to 3161da970d38cd6ed2ba8cadec93874d1d06e11e:
USB: serial: use variable for status (2016-07-16 12:45:39 +0200)
----------------------------------------------------------------
USB-serial updates for v4.8-rc1
Mostly clean ups, including the first few patches of a major overhaul of
the ti_usb_3410_5052 driver.
Included is also a new option-driver device id.
Signed-off-by: Johan Hovold <johan@xxxxxxxxxx>
----------------------------------------------------------------
Daniele Palmas (1):
USB: serial: option: add support for Telit LE910 PID 0x1206
Mathieu OTHACEHE (4):
USB: serial: ti_usb_3410_5052: remove useless comments
USB: serial: ti_usb_3410_5052: use __packed
USB: serial: ti_usb_3410_5052: remove ti_usb_3410_5052.h
USB: serial: ti_usb_3410_5052: use functions rather than macros
Muhammad Falak R Wani (1):
USB: serial: cp210x: use kmemdup
Oliver Neukum (1):
USB: serial: use variable for status
drivers/usb/serial/cp210x.c | 4 +-
drivers/usb/serial/generic.c | 18 ++-
drivers/usb/serial/option.c | 3 +
drivers/usb/serial/ti_usb_3410_5052.c | 271 ++++++++++++++++++++++++++++++----
drivers/usb/serial/ti_usb_3410_5052.h | 259 --------------------------------
5 files changed, 260 insertions(+), 295 deletions(-)
delete mode 100644 drivers/usb/serial/ti_usb_3410_5052.h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
