From: Peter Korsgaard <peter@korsgaard.com>
To: Javad Rahimipetroudi <javad.rahimipetroudi@essensium.com>
Cc: Marleen Vos <marleen.vos@mind.be>,
Javad Rahimipetroudi <javad.rahimipetroudi@mind.be>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 3/3] configs/avenger96: bump ATF version to v2.8
Date: Tue, 19 Mar 2024 08:38:23 +0100 [thread overview]
Message-ID: <87v85id634.fsf@48ers.dk> (raw)
In-Reply-To: <20240319070554.1323606-3-javad.rahimipetroudi@mind.be> (Javad Rahimipetroudi's message of "Tue, 19 Mar 2024 08:05:54 +0100")
>>>>> "Javad" == Javad Rahimipetroudi <javad.rahimipetroudi@essensium.com> writes:
> This patch upgrades the ATF version to v2.8. Please note that
> due to DTS chages from commit 51e223058fe70b311542178f1865514745fa7874
> ("feat(stm32mp15-fdts): add Avenger96 board with STM32MP157A DHCOR SoM")
> The ATF additional build variable also modified to use the new DTS file.
> Signed-off-by: Javad Rahimipetroudi <javad.rahimipetroudi@mind.be>
What about
board/arrow/avenger96/patches/arm-trusted-firmware/0001-stm32mp157a-avenger96.dts-enable-hash-device-to-unbr.patch?
Can that be dropped?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-19 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 7:05 [Buildroot] [PATCH v3 1/3] configs/avenger96: bump Uboot version to 2024.01 Javad Rahimipetroudi via buildroot
2024-03-19 7:05 ` [Buildroot] [PATCH v3 2/3] configs/avenger96: bump Linux version to 6.6.21LTS Javad Rahimipetroudi via buildroot
2024-03-19 7:05 ` [Buildroot] [PATCH v3 3/3] configs/avenger96: bump ATF version to v2.8 Javad Rahimipetroudi via buildroot
2024-03-19 7:38 ` Peter Korsgaard [this message]
2024-03-19 9:57 ` Javad Rahimipetroudi via buildroot
2024-03-19 8:47 ` Arnout Vandecappelle via buildroot
2024-03-19 10:28 ` Javad Rahimipetroudi via buildroot
2024-03-19 10:30 ` Peter Korsgaard
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=87v85id634.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=javad.rahimipetroudi@essensium.com \
--cc=javad.rahimipetroudi@mind.be \
--cc=marleen.vos@mind.be \
/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