All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Mason <jdmason@kudzu.us>
To: meta-arm@lists.yoctoproject.org,
	"emekcan.aras@arm.com" <emekcan.aras@arm.com>
Cc: Emekcan Aras <Emekcan.Aras@arm.com>, nd@arm.com
Subject: Re: [PATCH honister 0/3] arm-bsp/security: drop psa-arch-tests recipe
Date: Fri, 18 Feb 2022 08:32:17 -0500	[thread overview]
Message-ID: <164519113713.2418873.16795602415401250327.b4-ty@arm.com> (raw)
In-Reply-To: <20220217155953.2569183-1-emekcan.aras@arm.com>

On Thu, 17 Feb 2022 15:59:50 +0000, emekcan.aras@arm.com wrote:
> This change is to build and install psa-arch-tests using trusted-services code and drop psa-arch-tests recipe.
> 
> Signed-off-by: Vishnu Banavath vishnu.banavath@arm.com
> 
> Emekcan Aras (1):
>   kas/corstone1000-base: update meta-arm-image SHA
> 
> [...]

Applied, thanks!

[1/3] arm-bsp/security: drop psa-arch-tests recipe
      commit: 2e388235cb96bce4a42f63f266ab6a7ed04b8752
[2/3] arm-bsp/security: trusted-services to fix psa-arch-tests
      commit: 400bd5d5f4e8441878020fe51f3eaa78831b578e
[3/3] kas/corstone1000-base: update meta-arm-image SHA
      commit: 43e5b037e860e450ff4904c325452e5cbf79c13f

Best regards,
-- 
Jon Mason <jon.mason@arm.com>


  parent reply	other threads:[~2022-02-18 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 15:59 [PATCH honister 0/3] arm-bsp/security: drop psa-arch-tests recipe emekcan.aras
2022-02-17 15:59 ` [PATCH honister 1/3] " emekcan.aras
2022-02-17 15:59 ` [PATCH honister 2/3] arm-bsp/security: trusted-services to fix psa-arch-tests emekcan.aras
2022-02-17 15:59 ` [PATCH honister 3/3] kas/corstone1000-base: update meta-arm-image SHA emekcan.aras
2022-02-18 13:32 ` Jon Mason [this message]
2022-02-21 16:16 ` [PATCH honister 0/3] arm-bsp/security: drop psa-arch-tests recipe Jon Mason

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=164519113713.2418873.16795602415401250327.b4-ty@arm.com \
    --to=jdmason@kudzu.us \
    --cc=emekcan.aras@arm.com \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=nd@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.