From: David Woodhouse <dwmw2@infradead.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: UEFI Plugfest 2013 -- New Orleans
Date: Mon, 19 Aug 2013 09:25:35 +0100 [thread overview]
Message-ID: <1376900735.2322.26.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20130816152030.GL2133@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
On Fri, 2013-08-16 at 11:20 -0400, John W. Linville wrote:
> All,
>
> The Linux Foundation and The UEFI Forum are hosting a UEFI Plugfest
> event in New Orleans on September 19-20, 2013. This event will run
> concurrent with Linux Plumbers Conference, just after LinuxCon at the
> Hyatt Regency New Orleans.
Hm. It would be really useful to have a kernel build option which
*disables* all the workarounds we've ever put in for broken firmware.
Every deviation from the spec (or common sense), however minor, should
show up as a clear failure. Even the ones we *have* been able to work
around, because we still want them *fixed*.
And there's a school of thought that says we should brick as many
Samsung machines as possible, if they actually turn up without having
fixed that. A stress test for the NV storage is actually a really good
idea...
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5745 bytes --]
next prev parent reply other threads:[~2013-08-19 8:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 15:20 UEFI Plugfest 2013 -- New Orleans John W. Linville
2013-08-17 0:44 ` James Bottomley
2013-08-19 8:25 ` David Woodhouse [this message]
2013-08-19 12:55 ` Matthew Garrett
2013-08-19 15:22 ` James Bottomley
2013-08-19 16:00 ` Matthew Garrett
2013-08-19 17:02 ` James Bottomley
2013-08-19 17:21 ` Matthew Garrett
2013-08-19 17:38 ` James Bottomley
2013-08-19 17:47 ` Matthew Garrett
2013-08-19 20:09 ` David Woodhouse
2013-08-19 20:19 ` Matthew Garrett
2013-08-19 20:21 ` David Woodhouse
2013-08-19 20:39 ` Matthew Garrett
2013-08-19 21:06 ` David Woodhouse
2013-08-19 21:30 ` Matthew Garrett
2013-09-02 6:23 ` Matt Fleming
2013-08-19 15:17 ` Borislav Petkov
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=1376900735.2322.26.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).