From: ijc@debian.org (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/RFT PATCH 0/2] disable_hest quirk on HP m400 with bad UEFI firmwware
Date: Tue, 03 Jul 2018 18:16:12 +0100 [thread overview]
Message-ID: <1530638172.31922.25.camel@debian.org> (raw)
In-Reply-To: <20180703171251.GC11614@red-moon>
On Tue, 2018-07-03 at 18:12 +0100, Lorenzo Pieralisi wrote:
> I do not think anybody is preventing that, it is just that we do not
> see the reason for adding a DMI quirk to the mainline kernel to enable
> a platform with broken firmware that cripples one of the main feature
> it is supposed to implement, we can go on forever about this but that's
> the gist.
The quirk turns off a broken feature on the platform where it is
broken, not everywhere, there's no "crippling" of the feature.
Or are you suggesting that you have in mind a way to fix this which
makes HEST work even on m400 and renders the quirk unnecessary?
Ian.
next prev parent reply other threads:[~2018-07-03 17:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 10:06 [RFC/RFT PATCH 0/2] disable_hest quirk on HP m400 with bad UEFI firmwware James Morse
2018-06-28 10:06 ` [RFC/RFT PATCH 1/2] efi: Add helper to retrieve runtime version number James Morse
2018-06-28 10:06 ` [RFC/RFT PATCH 2/2] ACPI / APEI: Add DMI matching quirks for platforms that require hest_disable James Morse
2018-06-28 10:25 ` [RFC/RFT PATCH 0/2] disable_hest quirk on HP m400 with bad UEFI firmwware Ard Biesheuvel
2018-06-28 12:51 ` Lorenzo Pieralisi
2018-06-28 14:24 ` James Morse
2018-06-28 16:15 ` Geoff Levand
2018-06-28 20:56 ` Ard Biesheuvel
2018-07-03 8:46 ` Ian Campbell
2018-07-03 8:44 ` Ian Campbell
2018-07-03 15:17 ` Ard Biesheuvel
2018-07-03 15:47 ` Ian Campbell
2018-07-03 17:12 ` Lorenzo Pieralisi
2018-07-03 17:16 ` Ian Campbell [this message]
2018-07-03 17:39 ` Lorenzo Pieralisi
2018-07-03 19:47 ` Ian Campbell
2018-07-04 9:14 ` Lorenzo Pieralisi
2018-07-04 9:47 ` Ard Biesheuvel
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=1530638172.31922.25.camel@debian.org \
--to=ijc@debian.org \
--cc=linux-arm-kernel@lists.infradead.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).