public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Linn Crosetto <linn@hpe.com>
Cc: ard.biesheuvel@linaro.org, roy.franz@linaro.org,
	mingo@kernel.org, mark.rutland@arm.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] arm64/efi: query Secure Boot status according to UEFI spec
Date: Mon, 7 Mar 2016 14:08:52 +0000	[thread overview]
Message-ID: <20160307140852.GD27675@codeblueprint.co.uk> (raw)
In-Reply-To: <1457041550-15736-1-git-send-email-linn@hpe.com>

On Thu, 03 Mar, at 02:45:48PM, Linn Crosetto wrote:
> This series modifies the function that queries the status of UEFI Secure Boot
> in the EFI stub to match the UEFI specification, and allow the caller to
> determine if it is enabled, disabled, or in an unknown state due to an
> unexpected error from GetVariable().
> 
> v2:
>  - Add return values for unexpected errors
>  - Split changes into two patches
> 
> v3:
>  - Add more verbosity with additional prints
> 
> Linn Crosetto (2):
>   arm64/efi: report unexpected errors when determining Secure Boot status
>   arm64/efi: check SetupMode when determining Secure Boot status
> 
>  drivers/firmware/efi/libstub/arm-stub.c | 54 ++++++++++++++++++++++++++-------
>  1 file changed, 43 insertions(+), 11 deletions(-)
> 

Thanks Linn, I've picked these two patches up with Ard's and Mark's
tags.

      parent reply	other threads:[~2016-03-07 14:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  0:25 [PATCH] arm64/efi: check SetupMode when determining Secure Boot status Linn Crosetto
2016-02-24 11:23 ` Mark Rutland
2016-02-26  0:18 ` [PATCH v2 0/2] arm64/efi: query Secure Boot status according to UEFI spec Linn Crosetto
2016-02-26  0:18   ` [PATCH v2 1/2] arm64/efi: report unexpected errors when determining Secure Boot status Linn Crosetto
2016-03-03  8:03     ` Ard Biesheuvel
2016-02-26  0:18   ` [PATCH v2 2/2] arm64/efi: check SetupMode " Linn Crosetto
2016-03-02 13:38   ` [PATCH v2 0/2] arm64/efi: query Secure Boot status according to UEFI spec Matt Fleming
2016-03-03 21:45   ` [PATCH v3 " Linn Crosetto
2016-03-03 21:45     ` [PATCH v3 1/2] arm64/efi: report unexpected errors when determining Secure Boot status Linn Crosetto
2016-03-04  7:57       ` Ard Biesheuvel
2016-03-03 21:45     ` [PATCH v3 2/2] arm64/efi: check SetupMode " Linn Crosetto
2016-03-04  8:01       ` Ard Biesheuvel
2016-03-04 11:08     ` [PATCH v3 0/2] arm64/efi: query Secure Boot status according to UEFI spec Mark Rutland
2016-03-07 14:08     ` Matt Fleming [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-all 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=20160307140852.GD27675@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=ard.biesheuvel@linaro.org \
    --cc=linn@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@kernel.org \
    --cc=roy.franz@linaro.org \
    /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