From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/20] Implment a tty port structure and supporting logic
Date: Tue, 20 May 2008 10:23:30 -0700 [thread overview]
Message-ID: <20080520172330.GC11666@kroah.com> (raw)
In-Reply-To: <20080520015241.bd66fff0.akpm@linux-foundation.org>
On Tue, May 20, 2008 at 01:52:41AM -0700, Andrew Morton wrote:
> On Mon, 19 May 2008 09:50:49 -0700 Greg KH <greg@kroah.com> wrote:
>
> > On Mon, May 19, 2008 at 03:50:07PM +0100, Alan Cox wrote:
> > > Right now each tty has its own port level structure which means we can share
> > > no code between ports. Introduce a structure and some initial minor helper
> > > routines so that we can move towards commonality. In doing this the USB serial
> > > code gets a bit of shake up as it kept using port->tty unsafely. Fixing that
> > > means changing the API of all the USB serial drivers. On the bright side the
> > > API now looks far more like the tty layer API which will become useful later
> > > on.
> >
> > Very nice.
> >
> > If you don't mind, I'll be glad to take this through my tree as you are
> > touching the usb-serial drivers so much. Andrew, any objection to this?
>
> A lot depends on what else Alan is brewing up. I only have a single
> tty-related patch at present (remove-is_tty.patch) and a handful of
> possibly-related char driver patches
> (proper-extern-for-mwave_s_mdd.patch, if-0-hpet_unregister.patch and
> riscom8-remove-redundant-null-pointer-test.patch).
>
> But if a great mountain of tty- and/or char-related patches is
> forthcoming, that mountain will probably have a depencency upon your
> tree. And that's OK too, as long as you don't go and bugger up your
> tree and get it dropped from linux-next! Because if that happens I'll
> need to temporarily drop all the dependent patches and remember to
> restore them, which is always a bit sad.
That's up to Alan, I don't know what he has brewing for 2.6.27.
Alan?
thanks,
greg k-h
next prev parent reply other threads:[~2008-05-20 17:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 14:50 [PATCH 00/20] Implment a tty port structure and supporting logic Alan Cox
2008-05-19 14:50 ` [PATCH 01/20] tty: Introduce a tty_port common structure Alan Cox
2008-05-19 17:47 ` Sam Ravnborg
2008-05-19 17:51 ` Greg KH
2008-05-19 19:48 ` Alan Cox
2008-05-19 21:36 ` Greg KH
2008-05-19 14:50 ` [PATCH 02/20] tty: Clean up tiocmset Alan Cox
2008-05-19 14:50 ` [PATCH 03/20] epca: use tty_port Alan Cox
2008-05-19 14:50 ` [PATCH 04/20] isicom: " Alan Cox
2008-05-19 14:50 ` [PATCH 05/20] moxa: " Alan Cox
2008-05-19 14:50 ` [PATCH 06/20] mxser: " Alan Cox
2008-05-19 14:50 ` [PATCH 07/20] riscom8: " Alan Cox
2008-05-19 14:50 ` [PATCH 08/20] rocket: " Alan Cox
2008-05-19 14:50 ` [PATCH 09/20] synclink: " Alan Cox
2008-05-19 14:51 ` [PATCH 10/20] esp: " Alan Cox
2008-05-19 14:51 ` [PATCH 11/20] istallion: " Alan Cox
2008-05-19 14:51 ` [PATCH 12/20] stallion: " Alan Cox
2008-05-19 14:51 ` [PATCH 13/20] cyclades: " Alan Cox
2008-05-19 14:51 ` [PATCH 14/20] gs: " Alan Cox
2008-05-19 14:51 ` [PATCH 15/20] serial: " Alan Cox
2008-05-19 14:51 ` [PATCH 17/20] riscom8: remove bogus checks Alan Cox
2008-05-19 14:51 ` [PATCH 18/20] tty: add more tty_port fields Alan Cox
2008-05-19 14:51 ` [PATCH 19/20] whiteheat: coding style Alan Cox
2008-05-19 14:52 ` [PATCH 20/20] whiteheat: fix bugs found in the tidy and audit Alan Cox
2008-05-19 16:50 ` [PATCH 00/20] Implment a tty port structure and supporting logic Greg KH
2008-05-19 18:27 ` Alan Cox
2008-05-20 8:52 ` Andrew Morton
2008-05-20 17:23 ` Greg KH [this message]
2008-05-20 18:53 ` Alan Cox
2008-05-19 22:39 ` Aristeu Rozanski
2008-05-20 8:31 ` Alan Cox
2008-05-27 18:05 ` Greg KH
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=20080520172330.GC11666@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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