From: adam.johnston@arm.com
To: meta-arm@lists.yoctoproject.org, Ross.Burton@arm.com
Cc: nd@arm.com, Adam Johnston <adam.johnston@arm.com>
Subject: [PATCH 0/1] arm-bsp/corstone1000: Fix RSA key generation issue
Date: Fri, 19 Apr 2024 14:11:29 +0100 [thread overview]
Message-ID: <20240419131130.1988653-1-adam.johnston@arm.com> (raw)
From: Adam Johnston <adam.johnston@arm.com>
A patch was dropped when trusted-firmware-m was updated to 2.0 but it
had not yet been merged upstream (2.0 or master).
Adam Johnston (1):
arm-bsp/corstone1000: Fix RSA key generation issue
...tone1000-Increase-ITS-max-asset-size.patch | 27 +++++++++++++++++++
.../trusted-firmware-m-corstone1000.inc | 1 +
2 files changed, 28 insertions(+)
create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/0009-platform-corstone1000-Increase-ITS-max-asset-size.patch
next reply other threads:[~2024-04-19 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 13:11 adam.johnston [this message]
2024-04-19 13:11 ` [PATCH 1/1] arm-bsp/corstone1000: Fix RSA key generation issue adam.johnston
2024-04-20 22:43 ` [PATCH 0/1] " 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=20240419131130.1988653-1-adam.johnston@arm.com \
--to=adam.johnston@arm.com \
--cc=Ross.Burton@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 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).