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 09:46:18 +0100 [thread overview]
Message-ID: <1530607578.9841.126.camel@debian.org> (raw)
In-Reply-To: <CAKv+Gu8OkHZJL8FXhsfQP8JodWLTFg5kz4wVcDPVWTs-29buug@mail.gmail.com>
On Thu, 2018-06-28 at 22:56 +0200, Ard Biesheuvel wrote:
> But that does not make it an upstream problem. The fact that this is
> an EOL platform of which only a couple of hundred are in circulation,
> combined with the fact that there is a trivial workaround available
> (the command line option) makes it a non-issue in my opinion,
> especially given the fact that not a single distro ships pristine
> mainline kernels, and so they can carry the quirk themselves.
I think that's rather unfortunate given that many distros (Debian
included, AIUI Fedora too, I'm sure others) try to ship kernels as
close to mainline as possible and the general steer from the kernel
community to try and do so whenever possible, to track stable releases
early and often etc.
Ian.
next prev parent reply other threads:[~2018-07-03 8:46 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 [this message]
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
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=1530607578.9841.126.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).