From: Jon Mason <jdmason@kudzu.us>
To: meta-arm@lists.yoctoproject.org, Ross Burton <ross.burton@arm.com>
Cc: nd@arm.com
Subject: Re: [PATCH 1/5] arm-bsp/optee-os: set PV correctly for the corstone1000 build
Date: Wed, 18 May 2022 16:30:19 -0400 [thread overview]
Message-ID: <165290581935.1529216.2673912877323840123.b4-ty@arm.com> (raw)
In-Reply-To: <20220513141231.2513449-1-ross.burton@arm.com>
On Fri, 13 May 2022 15:12:27 +0100, Ross Burton wrote:
> The corstone1000 build of optee-os has a bbappend which uses a specific
> non-upstream branch of optee-os which is actually based on 3.10, so set
> PV appropriately in the recipe and update the PREFERRED_VERSION in
> corstone1000.inc.
Applied, thanks!
[1/5] arm-bsp/optee-os: set PV correctly for the corstone1000 build
commit: 4b94d77f693a0d21d01eb287d5a9757ecb5122b0
[2/5] arm-bsp/optee-test: clean up bbappends
commit: 6286e0d54cdc6edf9e1d03019fd9e0440f0d546f
[3/5] arm-bsp/optee-os: remove 3.16 bbappend
commit: 7e09d10e23f4bd92ab0d559e8c84b32ee949fa22
[4/5] arm-bsp/optee-client: remove bbappends
commit: 155a2f9ed4ff26d95ca0228d8d069062ac5bb4e4
[5/5] arm-bsp/optee-os-tadevkit: remove unused bbappend
commit: 79a20dc1d76fbd983365c29063eca64872b8ab1d
Best regards,
--
Jon Mason <jon.mason@arm.com>
prev parent reply other threads:[~2022-05-18 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 14:12 [PATCH 1/5] arm-bsp/optee-os: set PV correctly for the corstone1000 build Ross Burton
2022-05-13 14:12 ` [PATCH 2/5] arm-bsp/optee-test: clean up bbappends Ross Burton
2022-05-13 14:12 ` [PATCH 3/5] arm-bsp/optee-os: remove 3.16 bbappend Ross Burton
2022-05-13 14:12 ` [PATCH 4/5] arm-bsp/optee-client: remove bbappends Ross Burton
2022-05-13 14:12 ` [PATCH 5/5] arm-bsp/optee-os-tadevkit: remove unused bbappend Ross Burton
2022-05-16 16:45 ` [PATCH 1/5] arm-bsp/optee-os: set PV correctly for the corstone1000 build Jon Mason
2022-05-17 15:23 ` Jon Mason
2022-05-18 20:30 ` 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=165290581935.1529216.2673912877323840123.b4-ty@arm.com \
--to=jdmason@kudzu.us \
--cc=meta-arm@lists.yoctoproject.org \
--cc=nd@arm.com \
--cc=ross.burton@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.