From: "Kun Qin" <kuqin12@gmail.com>
To: Kun Qin <kuqin12@gmail.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v2 0/6] MM communicate functionality in variable policy
Date: Tue, 18 Jan 2022 10:40:39 -0800 [thread overview]
Message-ID: <22316.1642531239620402006@groups.io> (raw)
In-Reply-To: <20211221013334.1751-1-kuqin12@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 198 bytes --]
Hi ArmPkg maintainers,
It has been almost a month since this v2 patch series has been sent out for review. Could you please take a look and provide feedback? Thanks in advance.
Regards,
Kun
[-- Attachment #2: Type: text/html, Size: 218 bytes --]
next prev parent reply other threads:[~2022-01-18 18:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 1:33 [PATCH v2 0/6] MM communicate functionality in variable policy Kun Qin
2021-12-21 1:33 ` [PATCH v2 1/6] MdeModulePkg: VariableSmmRuntimeDxe: Fix Variable Policy Message Length Kun Qin
2022-01-11 1:18 ` 回复: [edk2-devel] " gaoliming
2021-12-21 1:33 ` [PATCH v2 2/6] MdePkg: MmCommunication2: Update MM communicate2 function description Kun Qin
2022-01-04 3:22 ` 回复: [edk2-devel] " gaoliming
2021-12-21 1:33 ` [PATCH v2 3/6] ArmPkg: MmCommunicationDxe: MM communicate function argument attributes Kun Qin
2021-12-21 1:33 ` [PATCH v2 4/6] ArmPkg: MmCommunicationDxe: Update MM communicate `CommBuffer**` checks Kun Qin
2021-12-21 1:33 ` [PATCH v2 5/6] ArmPkg: MmCommunicationDxe: Update MM communicate `CommSize` check Kun Qin
2021-12-21 1:33 ` [PATCH v2 6/6] ArmPkg: MmCommunicationDxe: Update MM communicate `MessageLength` check Kun Qin
2022-01-18 18:40 ` Kun Qin [this message]
2022-01-18 22:04 ` [edk2-devel] [PATCH v2 0/6] MM communicate functionality in variable policy Rebecca Cran
2022-01-18 22:06 ` Kun Qin
2022-01-19 7:59 ` Sami Mujawar
2022-01-19 9:37 ` Sami Mujawar
[not found] <16C2A13241682C7F.28461@groups.io>
2022-01-03 18:32 ` Kun Qin
2022-01-10 18:30 ` 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=22316.1642531239620402006@groups.io \
--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