From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Heorhi Valakhanovich <valahanovich@tut.by>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] tty: Only hangup once
Date: Tue, 19 Nov 2013 15:05:36 -0800 [thread overview]
Message-ID: <20131119230536.GA13504@kroah.com> (raw)
In-Reply-To: <528BD95B.3070400@hurleysoftware.com>
On Tue, Nov 19, 2013 at 04:34:19PM -0500, Peter Hurley wrote:
> On 11/19/2013 12:40 PM, Greg KH wrote:
> > It should be backported to 3.12, and any other kernels?
>
> Greg,
>
> This patch should apply cleanly to 3.12.
>
> The first commit to rely on the correct TTY_HUPPED state was
> commit 36697529b5bbe36911e39a6309e7a7c9250d280a,
> 'tty: Replace ldisc locking with ldisc_sem'
> which was introduced in the 3.12 cycle.
>
> Regards,
> Peter Hurley
>
> PS - Did you receive 'n_tty: Fix echo overrun tail computation'?
> I saw it didn't make 3.12.1.
Yes, I got it, I can't apply anything to my trees until 3.13-rc1 is out,
and because it's not in Linus's tree yet, I can't apply it to a stable
tree. So give us a few weeks, don't worry, it's not lost.
greg k-h
next prev parent reply other threads:[~2013-11-19 23:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 18:05 [PATCH] tty: Only hangup once Peter Hurley
2013-08-02 3:46 ` Greg Kroah-Hartman
2013-08-02 23:02 ` Peter Hurley
2013-11-17 17:38 ` Heorhi Valakhanovich
2013-11-18 13:42 ` One Thousand Gnomes
2013-11-18 17:37 ` Peter Hurley
2013-11-18 20:32 ` Peter Hurley
2013-11-18 21:09 ` Heorhi Valakhanovich
2013-11-19 13:46 ` Peter Hurley
2013-11-19 17:19 ` Heorhi Valakhanovich
2013-11-19 17:40 ` Greg KH
2013-11-19 21:34 ` Peter Hurley
2013-11-19 23:05 ` Greg KH [this message]
2013-11-18 23:03 ` One Thousand Gnomes
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=20131119230536.GA13504@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=valahanovich@tut.by \
/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).