public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: Kun Qin <kuqin12@gmail.com>
Cc: devel@edk2.groups.io, Hao A Wu <hao.a.wu@intel.com>,
	 Liming Gao <gaoliming@byosoft.com.cn>,
	Jian J Wang <jian.j.wang@intel.com>,
	 Leif Lindholm <quic_llindhol@quicinc.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	 Sami Mujawar <sami.mujawar@arm.com>
Subject: Re: [PATCH v3 0/2] Support MM based variable services in PEI for ARM
Date: Wed, 28 Jun 2023 20:44:00 +0200	[thread overview]
Message-ID: <CAMj1kXF8MLyWSohd9CvappDfq-KbThAHtLBdQH23yueQkuY0vg@mail.gmail.com> (raw)
In-Reply-To: <20230627231421.1956-1-kuqin12@gmail.com>

On Wed, 28 Jun 2023 at 01:14, Kun Qin <kuqin12@gmail.com> wrote:
>
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4464
>
> This patch series is a follow-up of previous submission:
> https://edk2.groups.io/g/devel/message/106372
>
> The main changes between v2 and v3 patches are:
>   - Removed header file for MM communicate PEI module
>   - Added constant qualifiers to applicable entries
>   - Added reviewed-by tag
>
> The change was verified on QEMU based ARM sbsa platform and proprietary
> hardware platform.
>
> Patch v3 branch: https://github.com/kuqin12/edk2/tree/arm_var_pei_v3
>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Leif Lindholm <quic_llindhol@quicinc.com>
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> Cc: Sami Mujawar <sami.mujawar@arm.com>
>
> Kun Qin (2):
>   ArmPkg: MmCommunicationPei: Introduce MM communicate in PEI
>   MdeModulePkg: Variable: Introduce MM based variable read service in
>     PEI
>

Thanks, I've queued this up now.


>  ArmPkg/Drivers/MmCommunicationPei/MmCommunicationPei.c          | 221 ++++++++++++
>  MdeModulePkg/Universal/Variable/MmVariablePei/MmVariablePei.c   | 381 ++++++++++++++++++++
>  ArmPkg/ArmPkg.dsc                                               |   2 +
>  ArmPkg/Drivers/MmCommunicationPei/MmCommunicationPei.inf        |  40 ++
>  MdeModulePkg/MdeModulePkg.dsc                                   |   1 +
>  MdeModulePkg/Universal/Variable/MmVariablePei/MmVariablePei.h   | 134 +++++++
>  MdeModulePkg/Universal/Variable/MmVariablePei/MmVariablePei.inf |  40 ++
>  7 files changed, 819 insertions(+)
>  create mode 100644 ArmPkg/Drivers/MmCommunicationPei/MmCommunicationPei.c
>  create mode 100644 MdeModulePkg/Universal/Variable/MmVariablePei/MmVariablePei.c
>  create mode 100644 ArmPkg/Drivers/MmCommunicationPei/MmCommunicationPei.inf
>  create mode 100644 MdeModulePkg/Universal/Variable/MmVariablePei/MmVariablePei.h
>  create mode 100644 MdeModulePkg/Universal/Variable/MmVariablePei/MmVariablePei.inf
>
> --
> 2.41.0.windows.1
>

  parent reply	other threads:[~2023-06-28 18:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 23:14 [PATCH v3 0/2] Support MM based variable services in PEI for ARM Kun Qin
2023-06-27 23:14 ` [PATCH v3 1/2] ArmPkg: MmCommunicationPei: Introduce MM communicate in PEI Kun Qin
2023-06-27 23:14 ` [PATCH v3 2/2] MdeModulePkg: Variable: Introduce MM based variable read service " Kun Qin
2023-06-28 18:44 ` Ard Biesheuvel [this message]
2023-06-28 20:00   ` [PATCH v3 0/2] Support MM based variable services in PEI for ARM Kun Qin

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=CAMj1kXF8MLyWSohd9CvappDfq-KbThAHtLBdQH23yueQkuY0vg@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