From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Jonathan Corbet <corbet@lwn.net>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Thomas Gleixner <tglx@linutronix.de>,
Magnus Damm <magnus.damm@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] sh: Revive BIOS earlyprintk support
Date: Thu, 19 Oct 2023 12:24:19 +0200 [thread overview]
Message-ID: <7877cb3f8deeb4ab4acf3dbcdc36ea7c7ef0d666.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <cover.1697708489.git.geert+renesas@glider.be>
Hi Geert!
On Thu, 2023-10-19 at 11:46 +0200, Geert Uytterhoeven wrote:
> SuperH BIOS earlyprintk support was accidently disabled.
> This series revives it, and records its existence in the documentation.
>
> This was tested on landisk using "earlyprintk=bios" and
> "earlyprintk=bios,keep".
>
> Thanks for your comments!
Thanks for catching this and fixing this! I will pick this up ASAP!
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2023-10-19 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 9:46 Geert Uytterhoeven
2023-10-19 9:46 ` [PATCH 1/2] sh: bios: Revive " Geert Uytterhoeven
2023-10-19 15:48 ` Randy Dunlap
2023-10-19 15:51 ` John Paul Adrian Glaubitz
2023-10-19 15:53 ` Randy Dunlap
2023-10-20 7:10 ` Geert Uytterhoeven
2023-10-24 16:42 ` John Paul Adrian Glaubitz
2023-10-19 9:46 ` [PATCH 2/2] Documentation: kernel-parameters: Add earlyprintk=bios on SH Geert Uytterhoeven
2023-10-24 16:42 ` John Paul Adrian Glaubitz
2023-10-19 10:24 ` John Paul Adrian Glaubitz [this message]
2023-10-25 14:54 ` [PATCH 0/2] sh: Revive BIOS earlyprintk support John Paul Adrian Glaubitz
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=7877cb3f8deeb4ab4acf3dbcdc36ea7c7ef0d666.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=corbet@lwn.net \
--cc=dalias@libc.org \
--cc=geert+renesas@glider.be \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®