From: Star Zeng <star.zeng@intel.com>
To: edk2-devel@lists.01.org
Cc: Star Zeng <star.zeng@intel.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: [PATCH 0/3] FirmwareManagement: Fix typo EFI_SECURITY_VIOLATIO
Date: Mon, 23 Apr 2018 15:00:38 +0800 [thread overview]
Message-ID: <1524466841-10204-1-git-send-email-star.zeng@intel.com> (raw)
Fix typo EFI_SECURITY_VIOLATIO to EFI_SECURITY_VIOLATION.
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Star Zeng (3):
MdePkg FirmwareManagement.h: Fix typo EFI_SECURITY_VIOLATIO
IntelSiliconPkg MicrocodeUpdate: Fix typo EFI_SECURITY_VIOLATIO
SignedCapsulePkg SystemFirmwareUpdate: Fix typo EFI_SECURITY_VIOLATIO
.../Feature/Capsule/MicrocodeUpdateDxe/MicrocodeFmp.c | 10 +++++-----
.../Feature/Capsule/MicrocodeUpdateDxe/MicrocodeUpdate.h | 10 +++++-----
MdePkg/Include/Protocol/FirmwareManagement.h | 13 +++++++------
.../SystemFirmwareUpdate/SystemFirmwareCommonDxe.c | 8 ++++----
.../Universal/SystemFirmwareUpdate/SystemFirmwareDxe.h | 10 +++++-----
.../SystemFirmwareUpdate/SystemFirmwareReportDxe.c | 2 +-
.../SystemFirmwareUpdate/SystemFirmwareUpdateDxe.c | 2 +-
7 files changed, 28 insertions(+), 27 deletions(-)
--
2.7.0.windows.1
next reply other threads:[~2018-04-23 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 7:00 Star Zeng [this message]
2018-04-23 7:00 ` [PATCH 1/3] MdePkg FirmwareManagement.h: Fix typo EFI_SECURITY_VIOLATIO Star Zeng
2018-04-23 7:00 ` [PATCH 2/3] IntelSiliconPkg MicrocodeUpdate: " Star Zeng
2018-04-23 7:00 ` [PATCH 3/3] SignedCapsulePkg SystemFirmwareUpdate: " Star Zeng
2018-04-23 7:38 ` [PATCH 0/3] FirmwareManagement: " Yao, Jiewen
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=1524466841-10204-1-git-send-email-star.zeng@intel.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