linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Paul Burton <paul.burton@imgtec.com>
Cc: <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Petr Mladek <pmladek@suse.com>,
	"Sergey Senozhatsky" <sergey.senozhatsky@gmail.com>,
	Borislav Petkov <bp@suse.de>, Tejun Heo <tj@kernel.org>,
	<linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] console: use first console if stdout-path device doesn't appear
Date: Sun, 30 Oct 2016 10:46:50 +0100	[thread overview]
Message-ID: <878tt6np85.fsf@linux-m68k.org> (raw)
In-Reply-To: <87mvi1cwly.fsf@linux-m68k.org> (Andreas Schwab's message of "Tue, 18 Oct 2016 20:58:49 +0200")

Any news?

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2016-10-30  9:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 12:50 [PATCH] console: Don't prefer first registered if DT specifies stdout-path Paul Burton
2016-08-09 14:12 ` kbuild test robot
2016-08-09 15:10 ` kbuild test robot
2016-08-09 15:19 ` [PATCH v2] " Paul Burton
2016-08-09 21:57   ` Andrew Morton
2016-10-16 18:07   ` Andreas Schwab
2016-10-17 10:33     ` Paul Burton
2016-10-17 17:39       ` Andreas Schwab
2016-10-18  9:18         ` [PATCH] console: use first console if stdout-path device doesn't appear Paul Burton
2016-10-18 18:58           ` Andreas Schwab
2016-10-30  9:46             ` Andreas Schwab [this message]
2016-10-31  5:28               ` Michael Ellerman
2016-10-31 12:14                 ` [PATCH v2] " Paul Burton
2016-10-31 15:50                   ` Paul Burton
2016-10-31 19:21                     ` Larry Finger
2016-10-31 23:09                     ` Sergey Senozhatsky
2016-10-31 23:31                       ` Larry Finger
2016-11-03 12:57                         ` [PATCH v3] " Paul Burton
2016-11-03 17:40                           ` Sergey Senozhatsky
2016-11-03 21:17                             ` Paul Burton
2016-11-04 15:44                               ` Sergey Senozhatsky
2016-11-04  8:05                           ` Andreas Schwab
     [not found]                           ` <8737j3n18r.fsf@concordia.ellerman.id.au>
2016-11-07  9:18                             ` Paul Burton
2016-11-07 15:26                               ` Larry Finger
2016-11-07 17:21                                 ` Paul Burton
2016-11-07 18:27                                   ` Larry Finger
2016-11-08 13:21                                     ` revert 05fd007e46296afb (was: [PATCH v3] console: use first console if stdout-path device doesn't appear) Sergey Senozhatsky
2016-11-03 13:04                         ` [PATCH v2] console: use first console if stdout-path device doesn't appear Paul Burton
2016-11-01  4:39                       ` Michael Ellerman
2016-10-31 15:58                   ` Larry Finger
2016-10-31 12:23                 ` [PATCH] " Paul Burton
2016-10-18  9:21         ` [PATCH v2] console: Don't prefer first registered if DT specifies stdout-path Paul Burton

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=878tt6np85.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paul.burton@imgtec.com \
    --cc=pmladek@suse.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).