From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Hurley <peter@hurleysoftware.com>
Subject: Re: 4.9 regression/bisection - 761ed4a94582 tty: serial_core: convert uart_close to use tty_port_close
Date: Fri, 21 Oct 2016 16:40:17 +0200 [thread overview]
Message-ID: <1477060817.8523.33.camel@gmail.com> (raw)
In-Reply-To: <CAL_JsqKsMdarvdfL6LTejmBQNK1uOrBtB9X+dscOeESJqx0C-A@mail.gmail.com>
On Fri, 2016-10-21 at 08:51 -0500, Rob Herring wrote:
> On Fri, Oct 21, 2016 at 7:45 AM, Mike Galbraith
> <umgwanakikbuti@gmail.com> wrote:
> > Greetings,
> >
> > My old DL980 G7 is exploding on reboot with master, with only the first
> > couple lines actually making it to the console. Once (and only once)
> > during bisection it did manage to get the below emitted.
>
> Does this patch[1] fix things for you? Sorry, only the reply seems to
> be in the archives.
Nope, still went boom.
---
drivers/tty/serial/serial_core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/drivers/tty/serial/serial_core.c
+++ b/drivers/tty/serial/serial_core.c
@@ -2746,8 +2746,6 @@ int uart_add_one_port(struct uart_driver
uport->cons = drv->cons;
uport->minor = drv->tty_driver->minor_start + uport->line;
- port->console = uart_console(uport);
-
/*
* If this port is a console, then the spinlock is already
* initialised.
@@ -2761,6 +2759,8 @@ int uart_add_one_port(struct uart_driver
uart_configure_port(drv, state, uport);
+ port->console = uart_console(uport);
+
num_groups = 2;
if (uport->attr_group)
num_groups++;
next prev parent reply other threads:[~2016-10-21 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 12:45 4.9 regression/bisection - 761ed4a94582 tty: serial_core: convert uart_close to use tty_port_close Mike Galbraith
2016-10-21 13:51 ` Rob Herring
2016-10-21 14:40 ` Mike Galbraith [this message]
2016-10-21 15:00 ` Rob Herring
2016-10-21 15:08 ` Mike Galbraith
2016-10-21 15:24 ` Mike Galbraith
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=1477060817.8523.33.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=robh@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