From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: James Bottomley
<James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
Cc: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
"John W. Linville"
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: UEFI Plugfest 2013 -- New Orleans
Date: Mon, 19 Aug 2013 18:47:43 +0100 [thread overview]
Message-ID: <20130819174743.GA25193@srcf.ucam.org> (raw)
In-Reply-To: <1376933926.2069.52.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
On Mon, Aug 19, 2013 at 10:38:46AM -0700, James Bottomley wrote:
> It's not about us removing the code, it's about us having an accurate
> compliance test. There are two reasons for having a fully correct
> compliance test
>
> 1. Our work arounds have unintended consequences which have knock
> on effects which mean that you don't know if a test failure is
> real or an unintended consequence of a work around.
It doesn't matter. If a platform is supposed to run Linux 3.6 then it
has to run Linux 3.6 regardless of whether or not the failure is due to
a firmware bug or a bug in the kernel. The platform vendor will be
obliged to fix it in the firmware no matter what the test suite says.
> 2. New features in specs tend to build on previous features, so
> we're going to have a hard time constructing accurate tests for
> layered features where we've done a work around for the base
> feature.
Which is easily rectified if the specification is modified to describe
reality instead.
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
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 18:47:43 +0100 [thread overview]
Message-ID: <20130819174743.GA25193@srcf.ucam.org> (raw)
In-Reply-To: <1376933926.2069.52.camel@dabdike.int.hansenpartnership.com>
On Mon, Aug 19, 2013 at 10:38:46AM -0700, James Bottomley wrote:
> It's not about us removing the code, it's about us having an accurate
> compliance test. There are two reasons for having a fully correct
> compliance test
>
> 1. Our work arounds have unintended consequences which have knock
> on effects which mean that you don't know if a test failure is
> real or an unintended consequence of a work around.
It doesn't matter. If a platform is supposed to run Linux 3.6 then it
has to run Linux 3.6 regardless of whether or not the failure is due to
a firmware bug or a bug in the kernel. The platform vendor will be
obliged to fix it in the firmware no matter what the test suite says.
> 2. New features in specs tend to build on previous features, so
> we're going to have a hard time constructing accurate tests for
> layered features where we've done a work around for the base
> feature.
Which is easily rectified if the specification is modified to describe
reality instead.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2013-08-19 17:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 15:20 UEFI Plugfest 2013 -- New Orleans John W. Linville
2013-08-16 15:20 ` John W. Linville
[not found] ` <20130816152030.GL2133-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2013-08-17 0:44 ` James Bottomley
2013-08-17 0:44 ` James Bottomley
2013-08-19 8:25 ` David Woodhouse
[not found] ` <1376900735.2322.26.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-08-19 12:55 ` Matthew Garrett
2013-08-19 12:55 ` Matthew Garrett
[not found] ` <20130819125507.GA19093-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-08-19 15:22 ` James Bottomley
2013-08-19 15:22 ` James Bottomley
2013-08-19 16:00 ` Matthew Garrett
[not found] ` <20130819160018.GA22532-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-08-19 17:02 ` James Bottomley
2013-08-19 17:02 ` James Bottomley
[not found] ` <1376931775.2069.46.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-08-19 17:21 ` Matthew Garrett
2013-08-19 17:21 ` Matthew Garrett
2013-08-19 17:38 ` James Bottomley
[not found] ` <1376933926.2069.52.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-08-19 17:47 ` Matthew Garrett [this message]
2013-08-19 17:47 ` Matthew Garrett
2013-08-19 20:09 ` David Woodhouse
2013-08-19 20:09 ` David Woodhouse
[not found] ` <1376942994.2322.39.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-08-19 20:19 ` Matthew Garrett
2013-08-19 20:19 ` Matthew Garrett
[not found] ` <20130819201952.GA28740-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-08-19 20:21 ` David Woodhouse
2013-08-19 20:21 ` David Woodhouse
[not found] ` <1376943671.2322.40.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-08-19 20:39 ` Matthew Garrett
2013-08-19 20:39 ` Matthew Garrett
[not found] ` <20130819203937.GA28967-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-08-19 21:06 ` David Woodhouse
2013-08-19 21:06 ` David Woodhouse
[not found] ` <1376946411.5087.2.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-08-19 21:30 ` Matthew Garrett
2013-08-19 21:30 ` Matthew Garrett
2013-09-02 7:42 ` Alex Elsayed
2013-09-02 6:23 ` Matt Fleming
2013-09-02 6:23 ` Matt Fleming
2013-08-19 15:17 ` Borislav Petkov
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=20130819174743.GA25193@srcf.ucam.org \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.