From: <Conor.Dooley@microchip.com>
To: <geert@linux-m68k.org>
Cc: <hch@lst.de>, <sfr@canb.auug.org.au>,
<linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>
Subject: Re: linux-next: Tree for May 3
Date: Mon, 16 May 2022 09:47:14 +0000 [thread overview]
Message-ID: <b930a399-fe49-7fe0-d4cd-34d7b71a9cf4@microchip.com> (raw)
In-Reply-To: <CAMuHMdVJuErxg16jFQEJhMwTgAt2AcHOGck1REZY6j0OpWwH+w@mail.gmail.com>
On 14/05/2022 13:18, Geert Uytterhoeven wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Hi Conor,
>
> On Wed, May 11, 2022 at 12:13 PM <Conor.Dooley@microchip.com> wrote:
>> [ 0.000000] Kernel command line: earlycon=sbi debug
>
> That should work without the "=sbi" part.
>
> I've used "earlycon" and "earlycon keep_bootcon" successfully on
> icicle before.
Yeah, honestly just entirely forgot I could do it without =sbi, d'oh.
Thanks for reminding me :)
The HSS is hogging the sbi console & that was what I was trying to kick.
next prev parent reply other threads:[~2022-05-16 9:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 7:29 linux-next: Tree for May 3 Stephen Rothwell
2022-05-04 8:32 ` Conor.Dooley
2022-05-09 13:33 ` Conor.Dooley
2022-05-09 14:11 ` Christoph Hellwig
2022-05-09 14:39 ` Conor.Dooley
2022-05-10 11:20 ` Conor.Dooley
2022-05-11 6:22 ` Christoph Hellwig
2022-05-11 6:44 ` Conor.Dooley
2022-05-11 6:48 ` Christoph Hellwig
2022-05-11 10:10 ` Conor.Dooley
2022-05-11 12:37 ` Christoph Hellwig
2022-05-11 14:08 ` Mike Rapoport
2022-05-11 14:10 ` Christoph Hellwig
2022-05-11 14:37 ` Mike Rapoport
2022-05-11 14:40 ` Christoph Hellwig
2022-05-13 7:55 ` Conor.Dooley
2022-05-14 12:18 ` Geert Uytterhoeven
2022-05-16 9:47 ` Conor.Dooley [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-03 7:17 Stephen Rothwell
2021-05-03 2:59 Stephen Rothwell
2019-05-03 10:00 Stephen Rothwell
2018-05-03 5:13 Stephen Rothwell
2017-05-03 5:54 Stephen Rothwell
2016-05-03 9:37 Stephen Rothwell
2013-05-03 4:10 Stephen Rothwell
2012-05-03 6:38 Stephen Rothwell
2011-05-03 5:47 Stephen Rothwell
2010-05-03 5:16 Stephen Rothwell
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=b930a399-fe49-7fe0-d4cd-34d7b71a9cf4@microchip.com \
--to=conor.dooley@microchip.com \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=sfr@canb.auug.org.au \
/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).