($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: anusmita.duttamazumder@arm.com
To: meta-arm@lists.yoctoproject.org
Cc: nd@arm.com, Anusmita Dutta Mazumder <anusmita.duttamazumder@arm.com>
Subject: [PATCH 0/2] arm-bsp/corstone1000: add unique guid for fvp and
Date: Wed, 10 Apr 2024 16:07:42 +0100	[thread overview]
Message-ID: <20240410150744.53421-1-anusmita.duttamazumder@arm.com> (raw)

From: Anusmita Dutta Mazumder <anusmita.duttamazumder@arm.com>

These patches set unique GUID for Corstone1000 FVP and
MPS3

Anusmita Dutta Mazumder (2):
  arm-bsp/u-boot:corstone1000: add unique guid for fvp and mps3
  arm-bsp/tf-m:corstone1000: add unique guid for fvp and mps3

 .../documentation/corstone1000/user-guide.rst |  4 +-
 ...orstone1000-add-unique-guid-for-mps3.patch | 41 +++++++++++++
 .../trusted-firmware-m-corstone1000.inc       |  1 +
 .../u-boot/u-boot-corstone1000.inc            |  1 +
 ...000-set-unique-GUID-for-fvp-and-mps3.patch | 57 +++++++++++++++++++
 5 files changed, 102 insertions(+), 2 deletions(-)
 create mode 100644 meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/0007-platform-corstone1000-add-unique-guid-for-mps3.patch
 create mode 100644 meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/0044-corstone1000-set-unique-GUID-for-fvp-and-mps3.patch

-- 
2.34.1



             reply	other threads:[~2024-04-10 15:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 15:07 anusmita.duttamazumder [this message]
2024-04-10 15:07 ` [PATCH 1/2] arm-bsp/u-boot:corstone1000: add unique guid for fvp and mps3 anusmita.duttamazumder
2024-04-10 15:07 ` [PATCH 2/2] arm-bsp/tf-m:corstone1000: " anusmita.duttamazumder
2024-04-11 18:39 ` [PATCH 0/2] arm-bsp/corstone1000: add unique guid for fvp and 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=20240410150744.53421-1-anusmita.duttamazumder@arm.com \
    --to=anusmita.duttamazumder@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).