From: Oliver Neukum <oneukum@suse.de>
To: Johan Hovold <johan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, Jim Paris <jim@jtan.com>,
linux-kernel@vger.kernel.org,
Peter Hurley <peter@hurleysoftware.com>
Subject: Re: [PATCH] USB: cdc-acm: only raise DTR on transitions from B0
Date: Thu, 30 Oct 2014 07:48:18 +0100 [thread overview]
Message-ID: <1414651698.21660.2.camel@linux-0dmf.site> (raw)
In-Reply-To: <20141029155840.GJ2265@localhost>
On Wed, 2014-10-29 at 16:58 +0100, Johan Hovold wrote:
> On Wed, Oct 29, 2014 at 11:56:02PM +0800, Greg Kroah-Hartman wrote:
> > This should go to older kernels as well, right?
>
> Yes, if you want.
>
> It's fixing handling of B0, but I doubt many people care (hence the
> missing stable tag). Note that set_termios is currently not called
> during open() (but Jim's patch will be relying on this one).
It may not hit many people, but whom it hits, it hits hard. It
should go into stable.
Regards
Oliver
next prev parent reply other threads:[~2014-10-30 8:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 23:26 [PATCH] cdc-acm: ensure that termios get set when the port is opened Jim Paris
2014-10-29 1:05 ` Peter Hurley
2014-10-29 13:43 ` [PATCH v2] cdc-acm: ensure that termios get set when the port is activated Jim Paris
2014-10-29 15:07 ` Johan Hovold
2014-10-29 15:30 ` [PATCH] USB: cdc-acm: only raise DTR on transitions from B0 Johan Hovold
2014-10-29 15:56 ` Greg Kroah-Hartman
2014-10-29 15:58 ` Johan Hovold
2014-10-30 0:53 ` [PATCH v3] cdc-acm: ensure that termios get set when the port is activated Jim Paris
2014-10-30 7:51 ` Johan Hovold
2014-10-30 14:45 ` [PATCH v4] " Jim Paris
2014-10-30 14:48 ` Johan Hovold
2014-10-30 15:04 ` [PATCH v4-real] " Jim Paris
2014-10-31 11:45 ` Johan Hovold
2014-10-31 16:04 ` Oliver Neukum
2014-10-30 6:48 ` Oliver Neukum [this message]
2014-11-05 17:41 ` [PATCH Resend] USB: cdc-acm: only raise DTR on transitions from B0 Johan Hovold
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=1414651698.21660.2.camel@linux-0dmf.site \
--to=oneukum@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=jim@jtan.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter@hurleysoftware.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.