From: Greg KH <greg@kroah.com>
To: Johan Hovold <johan@kernel.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 1/2] USB: serial: opticon: add chars_in_buffer() implementation
Date: Tue, 14 Jan 2020 13:18:47 +0100 [thread overview]
Message-ID: <20200114121847.GA1503960@kroah.com> (raw)
In-Reply-To: <20200114110146.5929-1-johan@kernel.org>
On Tue, Jan 14, 2020 at 12:01:45PM +0100, Johan Hovold wrote:
> Add a chars_in_buffer() implementation so that the tty layer will wait
> for outgoing buffered data to be drained when needed (e.g. on final
> close()).
>
> Signed-off-by: Johan Hovold <johan@kernel.org>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2020-01-14 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 11:01 [PATCH v2 1/2] USB: serial: opticon: add chars_in_buffer() implementation Johan Hovold
2020-01-14 11:01 ` [PATCH v2 2/2] USB: serial: opticon: stop all I/O on close() Johan Hovold
2020-01-14 12:18 ` Greg KH
2020-01-16 16:21 ` Johan Hovold
2020-01-14 12:18 ` Greg KH [this message]
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=20200114121847.GA1503960@kroah.com \
--to=greg@kroah.com \
--cc=johan@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).