From: Finn Thain <fthain@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Daniel Palmer <daniel@0x0f.com>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k/mvme147: Don't unregister boot console needlessly
Date: Sat, 29 Mar 2025 09:25:28 +1100 (AEDT) [thread overview]
Message-ID: <b8150223-8bce-32fb-c146-e14bcaa91134@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdUxe3gwsWdb37P+SOxL3twEf9_Fdr82naR+R3yxHCObOA@mail.gmail.com>
On Fri, 28 Mar 2025, Geert Uytterhoeven wrote:
> > --- a/arch/m68k/kernel/early_printk.c
> > +++ b/arch/m68k/kernel/early_printk.c
> > @@ -60,7 +60,7 @@ early_param("earlyprintk", setup_early_printk);
> >
> > static int __init unregister_early_console(void)
> > {
> > - if (!early_console || MACH_IS_MVME16x)
> > + if (!early_console || MACH_IS_MVME147 || MACH_IS_MVME16x)
> > return 0;
> >
> > return unregister_console(early_console);
>
> Perhaps the whole function and the late_initcall() can just be removed?
>
A comment in arch/m68k/kernel/early_printk.c gives the reason why that
code exists: debug_cons_nputs() lives in .init.text. Platforms like MVME
which don't use that function to implement earlyprintk don't have to worry
about this.
I suppose MACH_IS_FOO is not a great way to encode that requirement. But
it don't think it has to be self-documenting. It does have to be
consistent with the conditionals in head.S.
next prev parent reply other threads:[~2025-03-28 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 22:35 [PATCH] m68k/mvme147: Don't unregister boot console needlessly Finn Thain
2025-03-28 8:49 ` Geert Uytterhoeven
2025-03-28 22:25 ` Finn Thain [this message]
2025-03-31 8:44 ` Geert Uytterhoeven
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=b8150223-8bce-32fb-c146-e14bcaa91134@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=daniel@0x0f.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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