From: Jean Delvare <JDelvare@suse.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"macro@orcam.me.uk" <macro@orcam.me.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PING^6][PATCH 0/2] firmware: dmi: Avoid (some) empty names in kernel log
Date: Wed, 27 Apr 2022 15:19:46 +0000 [thread overview]
Message-ID: <d74f3f4b26c5620d726f0eebe4b0d14d923bea2b.camel@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2204271211090.9383@angie.orcam.me.uk>
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
next prev parent reply other threads:[~2022-04-27 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 23:24 [RESEND][PATCH 0/2] firmware: dmi: Avoid (some) empty names in kernel log Maciej W. Rozycki
2022-01-02 23:24 ` [RESEND][PATCH 1/2] firmware: dmi: Prevent empty board name from being logged Maciej W. Rozycki
2022-01-02 23:24 ` [RESEND][PATCH 2/2] firmware: dmi: Log board vendor if no system vendor has been given Maciej W. Rozycki
2022-02-01 10:49 ` [PING][PATCH 0/2] firmware: dmi: Avoid (some) empty names in kernel log Maciej W. Rozycki
2022-02-15 21:29 ` [PING^2][PATCH " Maciej W. Rozycki
2022-03-01 20:43 ` [PING^3][PATCH " Maciej W. Rozycki
2022-03-30 12:50 ` [PING^4][PATCH " Maciej W. Rozycki
2022-04-13 22:53 ` [PING^5][PATCH " Maciej W. Rozycki
2022-04-20 19:22 ` [PING^6][PATCH " Maciej W. Rozycki
[not found] ` <alpine.DEB.2.21.2204271211090.9383@angie.orcam.me.uk>
2022-04-27 15:19 ` Jean Delvare [this message]
2022-04-27 16:53 ` Maciej W. Rozycki
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=d74f3f4b26c5620d726f0eebe4b0d14d923bea2b.camel@suse.com \
--to=jdelvare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).