From: Jean Delvare <jdelvare@suse.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "firmware: dmi_scan: Use lowercase letters for UUID"
Date: Tue, 11 Dec 2018 14:49:27 +0100 [thread overview]
Message-ID: <1544536167.5269.7.camel@suse.com> (raw)
In-Reply-To: <87efaotgi1.fsf@dell.be.48ers.dk>
On Tue, 2018-12-11 at 13:06 +0100, Peter Korsgaard wrote:
> > > > > > "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>
> Hi Jean,
>
> >> Look, you can imagine that I was perfectly aware of what I was doing
> >> when I made that change, and that I pondered the decision carefully at
> >> that time. And my decision was that the change should be made. As far
> >> as I'm concerned, this ship has sailed already, sorry.
>
> > Sorry, what is the perceived risk of reverting this change? Just the
> > minor inconsistency between the dmidecode and sysfs output? As stated
> > above, the RFC requires conforming parsers to handle upper case as well.
>
> I would appreciate if you could explain what risk you see from reverting
> this change?
The exact same risk that you are complaining about, for a different
pair of kernel versions. You cannot at the same time argue that the
change should not have been done back then, and ask for same change to
be done again now.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2018-12-11 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 21:13 [PATCH] Revert "firmware: dmi_scan: Use lowercase letters for UUID" Peter Korsgaard
2018-12-05 21:36 ` Peter Korsgaard
2018-12-06 8:54 ` Jean Delvare
2018-12-06 9:22 ` Peter Korsgaard
2018-12-06 10:28 ` Jean Delvare
2018-12-06 15:46 ` Peter Korsgaard
2018-12-11 12:06 ` Peter Korsgaard
2018-12-11 13:49 ` Jean Delvare [this message]
2018-12-11 14:36 ` Peter Korsgaard
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=1544536167.5269.7.camel@suse.com \
--to=jdelvare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@korsgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox