From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: UEFI Plugfest 2013 -- New Orleans
Date: Mon, 19 Aug 2013 08:22:45 -0700 [thread overview]
Message-ID: <1376925765.2069.24.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <20130819125507.GA19093@srcf.ucam.org>
On Mon, 2013-08-19 at 13:55 +0100, Matthew Garrett wrote:
> On Mon, Aug 19, 2013 at 09:25:35AM +0100, David Woodhouse wrote:
>
> > 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*.
>
> Why? It's not like we can ever stop carrying that code.
The reason for doing it is that we have a buildable reference
implementation that's fully spec compliant we can then make the basis of
a test suite for UEFI.
I am worried about it from another angle, though: history has shown
we're not very good at maintaining configurations which we don't really
use ... since every distro will turn this off (or the workarounds on),
it's going to be a bit of work for someone to make sure it still
functions.
James
next prev parent reply other threads:[~2013-08-19 15:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 15:20 John W. Linville
2013-08-17 0:44 ` James Bottomley
2013-08-19 8:25 ` David Woodhouse
2013-08-19 12:55 ` Matthew Garrett
2013-08-19 15:22 ` James Bottomley [this message]
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=1376925765.2069.24.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=dwmw2@infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mjg59@srcf.ucam.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
all inboxes | Powered by JetHome®