From: Deepak Saxena <dsaxena@plexity.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] 8250: Don't restore NS16550 mode when console suspend is disabled
Date: Wed, 13 May 2009 00:34:51 +0000 [thread overview]
Message-ID: <20090513003451.GB28422@plexity.net> (raw)
In-Reply-To: <alpine.LFD.2.01.0905121452190.3343@localhost.localdomain>
On May 12 2009, at 15:00, Linus Torvalds was caught saying:
>
> Hmm. I already applied this, but then after looking closer, I undid that.
> Why? It looks buggy:
>
> > - if (up->capabilities & UART_NATSEMI) {
> > + if ((up->capabilities & UART_NATSEMI) &&
> > + (!uart_console(&up->port) && console_suspend_enabled)) {
> > unsigned char tmp;
>
> Isn't that second test wrong? Should it not be
>
> if ((up->capabilities & UART_NATSEMI) &&
> (console_suspend_enabled || !uart_console(&up->port)) {
>
> instead?
Yep, thinko on my end.
> /*
> * Suspend the uart port unless it's a console.
> *
> * But suspend even consoles if "console_suspend_enabled"
> * is set.
> */
> static inline int do_suspend_uart(struct uart_port *port)
> {
> return console_suspend_enabled || !uart_console(port);
> }
>
> and then make all these things (including the _existing_ cases in
> uart_suspend_port() use that helper function, rather than writing it out.
Sounds good. Alan?
~Deepak
--
In the end, they will not say, "those were dark times," they will ask
"why were their poets silent?" - Bertold Brecht
next prev parent reply other threads:[~2009-05-13 0:36 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
2009-05-13 0:34 ` Deepak Saxena [this message]
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=20090513003451.GB28422@plexity.net \
--to=dsaxena@plexity.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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