From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Gao, Liming" <gaoliming@byosoft.com.cn>,
Dionna Amalie Glaze <dionnaglaze@google.com>,
"Xu, Min M" <min.m.xu@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg: Correct memory type in PrePiDxeCis.h
Date: Mon, 30 Jan 2023 17:54:27 +0100 [thread overview]
Message-ID: <CAMj1kXGaz+v3CW_qU406kKN41DNO-zRLpjO6=CmH-jBNhgqVPQ@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB4929AA33C4C6C5ADD57BBD98D2D39@CO1PR11MB4929.namprd11.prod.outlook.com>
On Mon, 30 Jan 2023 at 17:27, Kinney, Michael D
<michael.d.kinney@intel.com> wrote:
>
> Hi Ard,
>
> Can you explain the process being followed here for content like this.
>
> The EDK II Code First Process as detailed below requires all content to only
> be added to edk2-staging repo and used from there before spec changes become
> public. Content is only added to the edk2 repo until after the spec with the
> change is public.
>
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Code-First-Process
>
> This process was reviewed and approved by the community. If there is a need
> for an alternate process, then that needs to be proposed, reviewed, and accepted.
>
Hello Mike,
I was not involved at all in the creation of these definitions. This
patch merely fixes the wrong index value that was introduced by
commit 502c01c5028038e4e6b4512e9c66be0ec4d11492
Author: Min M Xu <min.m.xu@intel.com>
Date: Tue Nov 1 13:13:43 2022 +0800
MdePkg: Add UEFI Unaccepted memory definition
RFC: https://bugzilla.tianocore.org/show_bug.cgi?id=3937
Plase refer to:
UEFI Spec v2.9 Table 7-5 Memory Type Usage before ExitBootServices()
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Zhiguang Liu <zhiguang.liu@intel.com>
Cc: Erdem Aktas <erdemaktas@google.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Cc: James Bottomley <jejb@linux.ibm.com>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>
Reviewed-by: Jiewen Yao <jiewen.yao@intel.com>
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
Signed-off-by: Min Xu <min.m.xu@intel.com>
next prev parent reply other threads:[~2023-01-30 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 19:21 [PATCH] MdeModulePkg: Correct memory type in PrePiDxeCis.h Dionna Glaze
2023-01-27 23:36 ` [edk2-devel] " Min Xu
2023-01-28 0:01 ` Dionna Glaze
2023-01-29 5:16 ` 回复: " gaoliming
2023-01-30 14:01 ` Ard Biesheuvel
2023-01-30 16:27 ` Michael D Kinney
2023-01-30 16:54 ` Ard Biesheuvel [this message]
2023-01-30 18:31 ` Michael D Kinney
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-list 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='CAMj1kXGaz+v3CW_qU406kKN41DNO-zRLpjO6=CmH-jBNhgqVPQ@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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