From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jiri Slaby <jslaby@suse.cz>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: No big TTY/serial patch merge for 3.6-rc1
Date: Thu, 26 Jul 2012 23:56:51 +0100 [thread overview]
Message-ID: <20120726235651.28a44eb1@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20120726212807.GA9049@kroah.com>
On Thu, 26 Jul 2012 14:28:07 -0700
Greg KH <gregkh@linuxfoundation.org> wrote:
> On Thu, Jul 26, 2012 at 10:23:13PM +0100, Alan Cox wrote:
> > On Thu, 26 Jul 2012 12:08:14 -0700
> > Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > > tty: Move the handling of the tty release logic
> >
> > Can we lose that one specifically. I've chased down Ian Abbotts problem
> > and replicated it and that is the offending patch not the lock localise
> > (which still needs to be kept out as it depends upon this one)
> >
> > I have it fixed but it's not had enough testing for -rc1 and moving the
> > termios data has enough spectacular hits all drivers fallout for 3.6
>
> Yes, I can go revert it. I'm working on building up a small tty-linus
> branch at the moment for just the "must haves" for 3.6. Right now it's
> just 10 patches listed below. Any objection to me sending these after
> a round trip through linux-next?
All look good to me
prev parent reply other threads:[~2012-07-26 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 19:08 Greg KH
2012-07-26 19:12 ` Jiri Slaby
2012-07-26 19:20 ` Greg KH
2012-07-26 19:21 ` Jiri Slaby
2012-07-26 19:17 ` Linus Torvalds
2012-07-26 21:23 ` Alan Cox
2012-07-26 21:28 ` Greg KH
2012-07-26 22:56 ` Alan Cox [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=20120726235651.28a44eb1@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®