From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Zeng, Star" <star.zeng@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [staging/FmpDevicePkg-master][PATCH] FmpDevicePkg FmpDxe: Return UNSUPPORTED if device has been locked
Date: Sun, 29 Jul 2018 16:39:39 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B8A9CD8C@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <1532786284-13512-1-git-send-email-star.zeng@intel.com>
Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>
Mike
> -----Original Message-----
> From: Zeng, Star
> Sent: Saturday, July 28, 2018 6:58 AM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star <star.zeng@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Subject: [staging/FmpDevicePkg-master][PATCH]
> FmpDevicePkg FmpDxe: Return UNSUPPORTED if device has
> been locked
>
> Instead of EFI_ACCESS_DENIED which is not defined in
> retval by
> UEFI spec, return UNSUPPORTED if device has been locked
> in
> SetTheImage().
>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Star Zeng <star.zeng@intel.com>
> ---
> FmpDevicePkg/FmpDxe/FmpDxe.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/FmpDevicePkg/FmpDxe/FmpDxe.c
> b/FmpDevicePkg/FmpDxe/FmpDxe.c
> index fb02e34f708f..b25a1511c70c 100644
> --- a/FmpDevicePkg/FmpDxe/FmpDxe.c
> +++ b/FmpDevicePkg/FmpDxe/FmpDxe.c
> @@ -928,7 +928,7 @@ SetTheImage (
> //
> if (mFmpDeviceLocked) {
> DEBUG ((DEBUG_ERROR, "FmpDxe: SetTheImage() -
> Device is already locked. Can't update.\n"));
> - Status = EFI_ACCESS_DENIED;
> + Status = EFI_UNSUPPORTED;
> goto cleanup;
> }
>
> --
> 2.7.0.windows.1
prev parent reply other threads:[~2018-07-29 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 13:58 [staging/FmpDevicePkg-master][PATCH] FmpDevicePkg FmpDxe: Return UNSUPPORTED if device has been locked Star Zeng
2018-07-29 16:39 ` Kinney, Michael D [this message]
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=E92EE9817A31E24EB0585FDF735412F5B8A9CD8C@ORSMSX113.amr.corp.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