[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1385142450.2884.1.camel@x230>
Date: Fri, 22 Nov 2013 17:47:31 +0000
From: Matthew Garrett <matthew.garrett@...ula.com>
To: "isimatu.yasuaki@...fujitsu.com" <isimatu.yasuaki@...fujitsu.com>
CC: "linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"matt.fleming@...el.com" <matt.fleming@...el.com>,
"jlee@...e.com" <jlee@...e.com>,
"matt@...sole-pimps.org" <matt@...sole-pimps.org>,
"richard@....at" <richard@....at>,
"cxie@...hat.com" <cxie@...hat.com>
Subject: Re: [PATCH] x86, efi: add efi_whitelist_table to use all efi
variable storage
On Fri, 2013-11-22 at 15:29 +0900, Yasuaki Ishimatsu wrote:
> + DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "PRIMEQUEST"),
Can we guarantee that no Primequests have this issue? Can we guarantee
that that no prior firmware versions have this issue? Can we guarantee
that no future firmware versions will have this issue?
--
Matthew Garrett <matthew.garrett@...ula.com>
Powered by blists - more mailing lists