From: Thomas Gleixner <tglx@kernel.org>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: Tim Bird <tim.bird@sony.com>,
pmladek@suse.com, rostedt@goodmis.org, john.ogness@linutronix.de,
senozhatsky@chromium.org, francesco@valla.it,
geert@linux-m68k.org, shashankbalaji02@gmail.com,
linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/1] printk: fix zero-valued printk timestamps in early boot
Date: Wed, 15 Apr 2026 23:30:36 +0200 [thread overview]
Message-ID: <87bjfjap37.ffs@tglx> (raw)
In-Reply-To: <CAJGKYO6Kk4+=9FEJYGxmBQhsB871ERaG0i33Pzx2BV-o7QDFJA@mail.gmail.com>
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.
Thanks,
tglx
next prev parent reply other threads:[~2026-04-15 21:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 20:37 [PATCH v4 0/1] printk: fix zero-valued printk timestamps Tim Bird
2026-04-10 20:37 ` [PATCH v4 1/1] printk: fix zero-valued printk timestamps in early boot Tim Bird
2026-04-12 10:10 ` kernel test robot
2026-04-13 17:58 ` Bird, Tim
2026-04-13 20:17 ` David Laight
2026-04-14 22:48 ` Thomas Gleixner
2026-04-12 11:12 ` kernel test robot
2026-04-12 12:55 ` kernel test robot
2026-04-14 7:03 ` Geert Uytterhoeven
2026-04-14 9:51 ` Roberto A. Foglietta
2026-04-14 22:38 ` Thomas Gleixner
2026-04-15 0:19 ` Roberto A. Foglietta
2026-04-15 9:19 ` Roberto A. Foglietta
2026-04-15 13:06 ` Roberto A. Foglietta
2026-04-15 18:40 ` Geert Uytterhoeven
2026-04-15 19:23 ` Roberto A. Foglietta
2026-04-15 21:30 ` Thomas Gleixner [this message]
2026-04-15 21:57 ` Roberto A. Foglietta
2026-04-15 22:24 ` Roberto A. Foglietta
2026-04-15 23:12 ` Bird, Tim
2026-04-16 5:38 ` Roberto A. Foglietta
2026-04-16 8:25 ` Roberto A. Foglietta
2026-04-16 8:43 ` Geert Uytterhoeven
2026-04-16 9:38 ` Roberto A. Foglietta
2026-04-16 10:52 ` David Laight
2026-04-17 7:35 ` Roberto A. Foglietta
2026-04-17 10:37 ` Petr Mladek
2026-04-17 11:46 ` Roberto A. Foglietta
2026-04-17 16:11 ` Steven Rostedt
2026-04-17 19:26 ` Roberto A. Foglietta
2026-04-17 19:24 ` Brian Masney
2026-04-17 19:52 ` Roberto A. Foglietta
2026-04-20 22:18 ` Bird, Tim
2026-04-21 8:33 ` Petr Mladek
2026-04-21 9:51 ` Roberto A. Foglietta
2026-04-21 14:07 ` Bird, Tim
2026-04-21 16:55 ` Roberto A. Foglietta
2026-04-27 23:33 ` Andrew Murray
2026-04-28 5:29 ` Bird, Tim
2026-04-28 5:56 ` Roberto A. Foglietta
2026-04-28 11:17 ` Andrew Murray
2026-04-28 13:27 ` 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=87bjfjap37.ffs@tglx \
--to=tglx@kernel.org \
--cc=francesco@valla.it \
--cc=geert@linux-m68k.org \
--cc=john.ogness@linutronix.de \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=roberto.foglietta@gmail.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=shashankbalaji02@gmail.com \
--cc=tim.bird@sony.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.