From: John Ogness <john.ogness@linutronix.de>
To: Vineet Gupta <vgupta@synopsys.com>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Shreyas Joshi <shreyas.joshi@biamp.com>,
shreyasjoshi15@gmail.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
linux-kernel@vger.kernel.org, buildroot@busybox.net,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-arch@vger.kernel.org,
arcml <linux-snps-arc@lists.infradead.org>
Subject: Re: ARC no console output (was Re: [PATCH 1/2] init/console: Use ttynull as a fallback when there is no console)
Date: Thu, 07 Jan 2021 10:08:09 +0106 [thread overview]
Message-ID: <8735zdm86m.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <d2a3b3c0-e548-7dd1-730f-59bc5c04e191@synopsys.com>
Hi Vineet,
On 2021-01-06, Vineet Gupta <vgupta@synopsys.com> wrote:
> This breaks ARC booting (no output on console).
Could you provide the kernel boot arguments that you use? This series is
partly about addressing users that have used boot arguments that are
technically incorrect (even if had worked). Seeing the boot arguments of
users that are not experiencing problems may help to reveal some of the
unusual console usages until now.
John Ogness
next prev parent reply other threads:[~2021-01-07 9:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 13:54 [PATCH 0/2] printk/console: Use ttynull when no console is available or wanted Petr Mladek
2020-11-11 13:54 ` [PATCH 1/2] init/console: Use ttynull as a fallback when there is no console Petr Mladek
2020-11-11 16:36 ` Greg Kroah-Hartman
2020-11-11 22:52 ` Guenter Roeck
2020-11-11 23:58 ` Sergey Senozhatsky
2020-11-12 0:17 ` Sergey Senozhatsky
2020-11-12 1:45 ` Sergey Senozhatsky
2020-11-16 16:20 ` Petr Mladek
2021-01-06 23:36 ` ARC no console output (was Re: [PATCH 1/2] init/console: Use ttynull as a fallback when there is no console) Vineet Gupta
2021-01-07 9:02 ` John Ogness [this message]
2021-01-07 13:14 ` Greg Ungerer
2021-01-07 16:43 ` Vineet Gupta
2021-01-07 17:04 ` Petr Mladek
2021-01-07 17:58 ` Vineet Gupta
2021-01-08 3:48 ` Sergey Senozhatsky
2021-01-08 5:18 ` Vineet Gupta
2021-01-08 9:30 ` Petr Mladek
2021-01-13 22:07 ` Peter Korsgaard
2021-01-07 9:09 ` Richard Weinberger
2021-01-07 12:48 ` Petr Mladek
2021-01-07 15:27 ` [Buildroot] " Yann E. MORIN
2020-11-11 13:54 ` [PATCH 2/2] printk/console: Allow to disable console output by using console="" or console=null Petr Mladek
2020-11-11 22:52 ` Guenter Roeck
2020-11-11 23:59 ` Sergey Senozhatsky
2020-11-20 14:24 ` [PATCH 0/2] printk/console: Use ttynull when no console is available or wanted Petr Mladek
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=8735zdm86m.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=buildroot@busybox.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=shreyas.joshi@biamp.com \
--cc=shreyasjoshi15@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=torvalds@linux-foundation.org \
--cc=vgupta@synopsys.com \
/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).