linux-kernel - Re: [PING^6][PATCH 0/2] firmware: dmi: Avoid (some) empty names in kernel log

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <d74f3f4b26c5620d726f0eebe4b0d14d923bea2b.camel@suse.com>
Date:   Wed, 27 Apr 2022 15:19:46 +0000
From:   Jean Delvare <JDelvare@...e.com>
To:     "torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
        "macro@...am.me.uk" <macro@...am.me.uk>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PING^6][PATCH 0/2] firmware: dmi: Avoid (some) empty names in
 kernel log

Hi Maciej,

>  I don't know if Jean means to continue maintaining the DMI subsystem, but 
> either way it looks to me like a stalemate.  I don't feel like it's a set 
> of changes that requires a lot of consideration, the situation is IMO 
> quite straightforward here and the result a clear improvement.

If you genuinely think that kernel patches should be applied without
being reviewed because they are "quite straightforward and the result
is a clear improvement" then I advise you refrain from touching kernel
code at all.

Jean is busy doing things that matter in other areas, things which
surprisingly are always more important than adding code to the kernel
to essentially slightly improve the format of an informative line in
the boot log of a 20-year old systems with crappy DMI data.

If you think this is the best use of your own time then you can keep
pinging me every other week for another year, but that's not going to
change my priorities. I'll eventually get to your patches when I have
less on my plate, regardless.

>  Can you therefore please advise who can review this patch series (I can 
> re-repost if needed) or otherwise how to proceed with this submission?

And no, bothering Linus to solve that kind of situation is NOT how
things work. Your patches have been posted publicly several times,
pinged way too many times already, yet nobody has shown any interest in
them. Maybe this means something.

-- 
Jean Delvare
SUSE L3 Support