public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Deepak Saxena <dsaxena@plexity.net>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8250: Don't restore NS16550 mode when console suspend is disabled
Date: Tue, 12 May 2009 18:01:33 -0700	[thread overview]
Message-ID: <1242176493.9718.76.camel@Joe-AcerAspire> (raw)
In-Reply-To: <20090513011842.22d9cd6c@lxorguk.ukuu.org.uk>

On Wed, 2009-05-13 at 01:18 +0100, Alan Cox wrote:
> > Hmm. I already applied this, but then after looking closer, I undid that. 
> > Why? It looks buggy:
> 
> I'm a bit suprised that as tty and serial maintainer this is the first
> time I see the patch.

Perhaps the MAINTAINERS entry for TTY should include
file patterns?

Would this be reasonable?

TTY LAYER
P:      Alan Cox
M:      alan@lxorguk.ukuu.org.uk
L:      linux-kernel@vger.kernel.org
L:      linux-serial@vger.kernel.org
S:      Maintained
F:      drivers/char/tty_*
F:      drivers/serial/serial_core.c
F:      linux/serial_core.h
F:      linux/serial.h
F:      linux/tty.h



  parent reply	other threads:[~2009-05-13  1:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 21:00 [PATCH] 8250: Don't restore NS16550 mode when console suspend is disabled Deepak Saxena
2009-05-12 22:00 ` Linus Torvalds
2009-05-13  0:18   ` Alan Cox
2009-05-13  0:28     ` Deepak Saxena
2009-05-13  8:44       ` Alan Cox
2009-05-13 14:58         ` Linus Torvalds
2009-05-13 15:35           ` Alan Cox
2009-05-13 18:04             ` Deepak Saxena
2009-05-13 18:46               ` Alan Cox
2009-05-18 18:24                 ` Deepak Saxena
2009-05-18 19:07                   ` Alan Cox
2009-05-13  1:01     ` Joe Perches [this message]
2009-05-13  0:34   ` Deepak Saxena
2009-05-12 22:08 ` 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=1242176493.9718.76.camel@Joe-AcerAspire \
    --to=joe@perches.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dsaxena@plexity.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --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