From: Matt Fleming <matt@codeblueprint.co.uk>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Taku Izumi <izumi.taku@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>, Tony Luck <tony.luck@intel.com>,
qiuxishi@huawei.com, kamezawa.hiroyu@jp.fujitsu.com,
Laszlo Ersek <lersek@redhat.com>, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH 1/2] efi: Add EFI_MEMORY_MORE_RELIABLE support to efi_md_typeattr_format()
Date: Tue, 25 Aug 2015 16:03:17 +0100 [thread overview]
Message-ID: <20150825150317.GB3013@codeblueprint.co.uk> (raw)
In-Reply-To: <CAKv+Gu81+bPKYAmSUtJ1fEF_9Tc8bOfmPSE8Kx4Ymv-HVojmdQ@mail.gmail.com>
On Tue, 25 Aug, at 04:23:10PM, Ard Biesheuvel wrote:
>
> Since its meaning is not at all obvious even when printing RELIABLE in
> full, couldn't we simply use 'MR' instead? You need the UEFI spec to
> make sense of this anyway ... (Same goes for RUN btw, perhaps RT would
> even be clearer there)
Fair point.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-08-25 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 17:15 [PATCH 0/2][RFC] Introduce "efi_fake_mem_mirror" boot option Taku Izumi
2015-08-20 17:15 ` [PATCH 1/2] efi: Add EFI_MEMORY_MORE_RELIABLE support to efi_md_typeattr_format() Taku Izumi
2015-08-25 14:18 ` Matt Fleming
2015-08-25 14:23 ` Ard Biesheuvel
2015-08-25 15:03 ` Matt Fleming [this message]
2015-08-20 17:16 ` [PATCH 2/2] x86, efi: Add "efi_fake_mem_mirror" boot option Taku Izumi
2015-08-25 23:46 ` Matt Fleming
2015-08-26 8:11 ` Izumi, Taku
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=20150825150317.GB3013@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lersek@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=qiuxishi@huawei.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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