From: Matt Fleming <matt@codeblueprint.co.uk>
To: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
jlee@suse.com, bp@alien8.de, ricardo.neri@intel.com,
ard.biesheuvel@linaro.org, ravi.v.shankar@intel.com,
fenghua.yu@intel.com
Subject: Re: [PATCH 0/4] UEFI: EFI_MEMORY_ATTRIBUTES_TABLE support for x86
Date: Wed, 7 Dec 2016 20:04:08 +0000 [thread overview]
Message-ID: <20161207200408.GC5462@codeblueprint.co.uk> (raw)
In-Reply-To: <1481137266.15606.131.camel@intel.com>
On Wed, 07 Dec, at 11:01:06AM, Sai Praneeth Prakhya wrote:
>
> Thanks Matt!
>
> Would you like to see a new version of these patch series addressing
> your comments? Like
> 1. Dropping of patch #4
> 2. Adding Reviewed-by tag of Joey (Sorry for that)
> 3. This time with correct version number
No need, they're already in the 'next' branch of the EFI tree.
next prev parent reply other threads:[~2016-12-07 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 19:15 [PATCH 0/4] UEFI: EFI_MEMORY_ATTRIBUTES_TABLE support for x86 Sai Praneeth Prakhya
2016-12-06 19:16 ` [PATCH 1/4] efi: Make EFI_MEMORY_ATTRIBUTES_TABLE initialization common across all architectures Sai Praneeth Prakhya
2016-12-07 13:28 ` Matt Fleming
2016-12-06 19:16 ` [PATCH 2/4] efi: Introduce EFI_MEM_ATTR bit and set it from memory attributes table Sai Praneeth Prakhya
2016-12-06 19:16 ` [PATCH 3/4] x86/efi: Add support for EFI_MEMORY_ATTRIBUTES_TABLE Sai Praneeth Prakhya
2016-12-06 19:16 ` [PATCH 4/4] efi: Skip parsing of EFI_PROPERTIES_TABLE if EFI_MEMORY_ATTRIBUTES_TABLE is detected Sai Praneeth Prakhya
2016-12-07 13:36 ` Matt Fleming
2016-12-07 13:26 ` [PATCH 0/4] UEFI: EFI_MEMORY_ATTRIBUTES_TABLE support for x86 Matt Fleming
2016-12-07 13:56 ` Matt Fleming
2016-12-07 19:01 ` Sai Praneeth Prakhya
2016-12-07 20:04 ` Matt Fleming [this message]
2016-12-07 20:13 ` Sai Praneeth Prakhya
2016-12-13 6:47 ` joeyli
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=20161207200408.GC5462@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=jlee@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri@intel.com \
--cc=sai.praneeth.prakhya@intel.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).