From: Finn Thain <fthain@linux-m68k.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Mike Rapoport <rppt@kernel.org>, Sam Creasey <sammy@sammy.net>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Enable memtest kernel parameter
Date: Thu, 11 Nov 2021 17:20:56 +1100 (AEDT) [thread overview]
Message-ID: <fc341bdf-a145-3a6b-5325-eb8dce2f1cf4@linux-m68k.org> (raw)
In-Reply-To: <725c0578-d816-f0c9-175a-7400c4a01887@infradead.org>
On Wed, 10 Nov 2021, Randy Dunlap wrote:
> On 11/10/21 5:10 PM, Finn Thain wrote:
> > Enable the memtest feature and rearrange some code to prevent it from
> > clobbering the initrd.
> >
> > The CONFIG_BLK_DEV_INITRD symbol was conditional on !defined(CONFIG_SUN3).
> > For simplicity, remove that test on the basis that m68k_ramdisk.size == 0
> > on Sun 3.
> >
> > The SLIME source code athttp://sammy.net/ shows that no BI_RAMDISK entry
> > is ever passed to the kernel due to #ifdef 0 around the relevant code.
> >
> > Cc: Mike Rapoport<rppt@kernel.org>
> > Cc: Sam Creasey<sammy@sammy.net>
> > Signed-off-by: Finn Thain<fthain@linux-m68k.org>
> > ---
> > Are there any other Linux bootloaders on Sun 3?
> > ---
> > arch/m68k/Kconfig | 1 +
> > arch/m68k/kernel/setup_mm.c | 15 ++++++---------
> > arch/m68k/mm/motorola.c | 2 ++
> > 3 files changed, 9 insertions(+), 9 deletions(-)
>
> Hi Finn,
>
> Please also update Documentation/admin-guide/kernel-parameters.txt:
>
> memtest= [KNL,X86,ARM,PPC,RISCV] Enable memtest
>
> to include "M68K".
>
> thanks.
>
Will do.
Thanks for your review.
prev parent reply other threads:[~2021-11-11 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 1:10 [PATCH] m68k: Enable memtest kernel parameter Finn Thain
2021-11-11 2:04 ` Randy Dunlap
2021-11-11 6:20 ` Finn Thain [this message]
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=fc341bdf-a145-3a6b-5325-eb8dce2f1cf4@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=sammy@sammy.net \
/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