From: "Michael Kubacki" <michael.kubacki@outlook.com>
To: devel@edk2.groups.io
Cc: Liming Gao <liming.gao@intel.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: [PATCH v1 0/7] FmpDevicePkg Minor Fixes
Date: Thu, 30 Jul 2020 20:14:41 -0700 [thread overview]
Message-ID: <MWHPR07MB3440DA4371A067BF43E39014E94E0@MWHPR07MB3440.namprd07.prod.outlook.com> (raw)
From: Michael Kubacki <michael.kubacki@microsoft.com>
REF:https://bugzilla.tianocore.org/show_bug.cgi?id=2869
This patch series makes minor fixes and enhancements in
FmpDevicePkg. None of the issues impact functionality in a
major way.
These are smaller sets of changes that are being submitted prior
to a larger future patch series that will cover functional changes
for BZ2802.
Please check the git notes in patch 3 and patch 5.
Cc: Liming Gao <liming.gao@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Michael Kubacki (7):
FmpDevicePkg/FmpDependencyLib: Correct ValidateDependency()
documentation
FmpDevicePkg/FmpDependencyLib: Fix "exression" typo
FmpDevicePkg/FmpDependencyLib: Handle version string overflow
FmpDevicePkg/FmpDependencyCheckLib: Return unsatisfied on handle
failure
FmpDevicePkg/FmpDxe: Better warn of potential ImageTypeId misconfig
FmpDevicePkg/FmpDxe: Indicate ESRT GUID on invalid ImageIdName
FmpDevicePkg/FmpDxe: Improve function parameter validation
FmpDevicePkg/FmpDxe/FmpDxe.c | 62 ++++++++++++++++----
FmpDevicePkg/Library/FmpDependencyCheckLib/FmpDependencyCheckLib.c | 2 +
FmpDevicePkg/Library/FmpDependencyLib/FmpDependencyLib.c | 8 ++-
FmpDevicePkg/FmpDxe/FmpDxe.h | 10 ++--
FmpDevicePkg/Include/Library/FmpDependencyLib.h | 5 +-
5 files changed, 67 insertions(+), 20 deletions(-)
--
2.27.0.windows.1
next reply other threads:[~2020-07-31 3:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 3:14 Michael Kubacki [this message]
2020-07-31 6:56 ` [edk2-devel] [PATCH v1 0/7] FmpDevicePkg Minor Fixes Xu, Wei6
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=MWHPR07MB3440DA4371A067BF43E39014E94E0@MWHPR07MB3440.namprd07.prod.outlook.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