From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: linux-usb@vger.kernel.org, Felipe Balbi <balbi@kernel.org>
Subject: [v3,3/5] usb: gadget: u_serial: make OBEX port not a console
Date: Wed, 27 Feb 2019 14:06:58 +0100 [thread overview]
Message-ID: <20190227130658.GC18700@kroah.com> (raw)
On Wed, Feb 27, 2019 at 11:46:58AM +0100, Michał Mirosław wrote:
> Prevent OBEX serial port from ever becoming a console. Console messages
> will definitely break the protocol, and since you have to instantiate
> the port making it explicitly for OBEX, there is no point in allowing
> console to break it by mistake.
>
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
Much saner api, thanks for making these changes.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next reply other threads:[~2019-02-27 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 13:06 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-27 10:46 [v3,3/5] usb: gadget: u_serial: make OBEX port not a console Michał Mirosław
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=20190227130658.GC18700@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
/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).