From: Corey Minyard <minyard@acm.org>
To: Johan Hovold <johan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] USB: serial: return errors from break handling
Date: Sun, 4 Jun 2023 15:19:16 -0500 [thread overview]
Message-ID: <ZHzxxOvUvTfl1ATL@mail.minyard.net> (raw)
In-Reply-To: <20230604123505.4661-1-johan@kernel.org>
On Sun, Jun 04, 2023 at 02:35:02PM +0200, Johan Hovold wrote:
> This series starts returning errors from break handling and also uses
> that mechanism to report to user space when break signalling is not
> supported (e.g. when device or driver support is missing).
>
> Note that the tty layer currently returns early but without reporting
> errors when a tty driver does not support break signalling. The intent
> expressed in commit 9e98966c7bb9 ("tty: rework break handling") from
> 2008 appears to be to allow missing support to be reported to user
> space however.
This worked as expected for me.
Tested-by: Corey Minyard <cminyard@mvista.com>
>
> Johan
>
>
> Changes in v2
> - fix return of potentially uninitialised status variable in
> io_edgeport as reported by kernel test robot <lkp@intel.com> and Dan
> Carpenter:
>
> https://lore.kernel.org/all/202306031014.qzAY3uQ6-lkp@intel.com/
>
>
> 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/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 +-
> 25 files changed, 147 insertions(+), 73 deletions(-)
>
> --
> 2.39.3
>
next prev parent reply other threads:[~2023-06-04 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 12:35 [PATCH v2 0/3] USB: serial: return errors from break handling Johan Hovold
2023-06-04 12:35 ` [PATCH v2 1/3] " Johan Hovold
2023-06-06 11:13 ` Oliver Neukum
2023-06-06 11:34 ` Johan Hovold
2023-06-04 12:35 ` [PATCH v2 2/3] USB: serial: cp210x: disable break signalling on CP2105 SCI Johan Hovold
2023-06-04 12:35 ` [PATCH v2 3/3] USB: serial: report unsupported break signalling Johan Hovold
2023-06-04 20:19 ` Corey Minyard [this message]
2023-06-06 11:18 ` [PATCH v2 0/3] USB: serial: return errors from break handling Oliver Neukum
2023-06-06 11:39 ` Johan Hovold
2023-06-06 12:46 ` Corey Minyard
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=ZHzxxOvUvTfl1ATL@mail.minyard.net \
--to=minyard@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.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;
as well as URLs for NNTP newsgroup(s).