From: Jon Mason <jdmason@kudzu.us>
To: meta-arm@lists.yoctoproject.org, harsimransingh.tungal@arm.com
Subject: Re: [PATCH 0/3] corstone1000:arm-bsp: Enable SMM gateway authenticated variables and Secure Boot
Date: Tue, 30 Apr 2024 22:06:55 -0400 [thread overview]
Message-ID: <171452921863.3441774.16122913171709152640.b4-ty@arm.com> (raw)
In-Reply-To: <20240430154654.26833-1-harsimransingh.tungal@arm.com>
On Tue, 30 Apr 2024 16:46:51 +0100, harsimransingh.tungal@arm.com wrote:
> From: Harsimran Singh Tungal <harsimransingh.tungal@arm.com>
>
> These changes enable the SMM gateway authenticated variables and Secure Boot features
> implementation for Corstone-1000
>
> Emekcan Aras (1):
> arm-bsp/trusted-firmware-a: corstone1000: Remove unused NS_SHARED_RAM
> region
>
> [...]
Applied, thanks!
[1/3] arm-bsp: corstone1000: Enable SMM gateway authenticated variables
commit: 12711d573479519dbabac2452aa132a95d5d7d10
[2/3] arm-bsp/u-boot: corstone1000: Enable UEFI secure boot
commit: 25eec5ced277a9a9880485e80c43dacd398ccfdb
[3/3] arm-bsp/trusted-firmware-a: corstone1000: Remove unused NS_SHARED_RAM region
commit: e20aac1b6b2dcb9ef38c79c7b52e4b5c2a1be4c4
Best regards,
--
Jon Mason <jon.mason@arm.com>
prev parent reply other threads:[~2024-05-01 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 15:46 [PATCH 0/3] corstone1000:arm-bsp: Enable SMM gateway authenticated variables and Secure Boot harsimransingh.tungal
2024-04-30 15:46 ` [PATCH 1/3] arm-bsp: corstone1000: Enable SMM gateway authenticated variables harsimransingh.tungal
2024-04-30 15:46 ` [PATCH 2/3] arm-bsp/u-boot: corstone1000: Enable UEFI secure boot harsimransingh.tungal
2024-04-30 15:46 ` [PATCH 3/3] arm-bsp/trusted-firmware-a: corstone1000: Remove unused NS_SHARED_RAM region harsimransingh.tungal
2024-05-01 2:06 ` Jon Mason [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=171452921863.3441774.16122913171709152640.b4-ty@arm.com \
--to=jdmason@kudzu.us \
--cc=harsimransingh.tungal@arm.com \
--cc=meta-arm@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).