public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kun Qin" <kuqin12@gmail.com>
To: devel@edk2.groups.io, Jian J Wang <jian.j.wang@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>,
	Hao A Wu <hao.a.wu@intel.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Zhiguang Liu <zhiguang.liu@intel.com>,
	Leif Lindholm <leif@nuviainc.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>
Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>,
	Michael Kubacki <michael.kubacki@microsoft.com>
Subject: Re: [edk2-devel] [PATCH v2 0/6] MM communicate functionality in variable policy
Date: Mon, 3 Jan 2022 10:32:13 -0800	[thread overview]
Message-ID: <6892acc9-0ce2-9970-76e2-2ab2d56497d5@gmail.com> (raw)
In-Reply-To: <16C2A13241682C7F.28461@groups.io>

Hi MdePkg, MdeModulePkg and ArmPkg maintainers,

Happy new year!

It has been a while since this v2 patch series has been sent out for 
review. Could you please take a look and provide feedback? Any input is 
appreciated.

Regards,
Kun

On 12/20/2021 17:33, Kun Qin via groups.io wrote:
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3709
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3751
> 
> This patch series is a follow up of previous submission:
> https://edk2.groups.io/g/devel/message/84140
> 
> v2 patches mainly focus on feedback for commits submitted in v1 patches:
> a. Splitted the original ArmPkg patch into 4 separate patches;
> b. Updated patches according to Uncrustify scanning results;
> 
> Patch v2 branch: https://github.com/kuqin12/edk2/tree/mm_communicate_check_v2
> 
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Zhiguang Liu <zhiguang.liu@intel.com>
> Cc: Leif Lindholm <leif@nuviainc.com>
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
> Cc: Michael Kubacki <michael.kubacki@microsoft.com>
> 
> Kun Qin (6):
>    MdeModulePkg: VariableSmmRuntimeDxe: Fix Variable Policy Message
>      Length
>    MdePkg: MmCommunication2: Update MM communicate2 function description
>    ArmPkg: MmCommunicationDxe: MM communicate function argument
>      attributes
>    ArmPkg: MmCommunicationDxe: Update MM communicate `CommBuffer**`
>      checks
>    ArmPkg: MmCommunicationDxe: Update MM communicate `CommSize` check
>    ArmPkg: MmCommunicationDxe: Update MM communicate `MessageLength`
>      check
> 
>   ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c               | 46 ++++++++++++--------
>   MdeModulePkg/Universal/Variable/RuntimeDxe/VariablePolicySmmDxe.c | 10 ++---
>   MdePkg/Include/Protocol/MmCommunication2.h                        | 13 +++---
>   3 files changed, 41 insertions(+), 28 deletions(-)
> 

       reply	other threads:[~2022-01-03 18:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16C2A13241682C7F.28461@groups.io>
2022-01-03 18:32 ` Kun Qin [this message]
2022-01-10 18:30   ` [edk2-devel] [PATCH v2 0/6] MM communicate functionality in variable policy Kun Qin
2021-12-21  1:33 Kun Qin
2022-01-18 18:40 ` [edk2-devel] " Kun Qin
2022-01-18 22:04   ` Rebecca Cran
2022-01-18 22:06     ` Kun Qin
2022-01-19  7:59       ` Sami Mujawar
2022-01-19  9:37 ` Sami Mujawar

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=6892acc9-0ce2-9970-76e2-2ab2d56497d5@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