Re: [PATCH v4 1/1] printk: fix zero-valued printk timestamps in early boot

[Roberto A. Foglietta]

On Wed, 15 Apr 2026 at 23:30, Thomas Gleixner <tglx@xxxxxxxxxx> wrote:
>
> On Wed, Apr 15 2026 at 02:19, Roberto A. Foglietta wrote:
> > While keeping architectures separate is for abstraction layer best
> > practice, in very specific cases abstraction can be a meaningless
> > concept or much less important than having a single file for a single
> > feature (the complementary way of organising stuff). Because in Linux
> > the abstraction layer approach applies for architectures, the gap
> > between aesthetic and a specific case like an early boot macros set
> > hack for debugging is to clarify the exception from the general rule
> > in the header itself.
>
> Please spare me this AI bullsh*t.
>
> There is absolutely ZERO justification for this at all. End of story.
>

V5

A single file with the essential for hacking the early boot,
activatable by debug export menuconfig, an #include "locale.h" in the
same folder in which printk.c lives and when the developer did every
insanity to make things work, rm -f $file and push all. No one in
production nor users will complain that there is a Kconfig debug
expert feature potentially broken. No one among kernel janitors will
need to care about an isolated file in which the whole future changes
acceptable are extending the framework to another architecture
maintaining the essential simplicity of reading a register protected
by a fence to grant WHEN it would be read.

! AI bullsh*t.

Beware of activating debug expert options, crying isn't allowed in
adulthood... What you call bullshit is simplicity for both the worlds.
The speed at which I am writing about things you cannot compute as
fast as I can write, has nothing to do with AI. Try to compile your
metacognition.ko with -O2 option instead of -xxs... LOL (yes this last
paragraph is a bullsh*t, so we can have a comparison between the
prototype and the instance of the BS class/template LOLx2).

Best regards, R-