From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-amarula@amarulasolutions.com,
Bartosz Bilas <b.bilas@grinn-global.com>,
Raphael Gallais-Pou <rgallaispou@gmail.com>,
Marleen Vos <marleen.vos@mind.be>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] configs/stm32mp157a_dk1: bump Linux to 6.9.8 and TF-A to 2.9
Date: Sun, 14 Jul 2024 17:08:17 +0200 [thread overview]
Message-ID: <20240714170817.63dfd93f@windsurf> (raw)
In-Reply-To: <20240713215218.2665512-1-dario.binacchi@amarulasolutions.com>
On Sat, 13 Jul 2024 23:52:17 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> The patch, following the suggestion expressed in [1], aligns the
> software versions of stm32mp157a_dk1 to stm32mp157c_dk2. Indeed, the two
> boards have many more similarities than differences.
>
> [1] https://patchwork.ozlabs.org/project/buildroot/patch/20240713130847.4097389-1-dario.binacchi@amarulasolutions.com
> Suggested-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> .../arm-trusted-firmware/arm-trusted-firmware.hash | 2 +-
> .../stm32mp157a-dk1/patches/linux/linux.hash | 2 +-
> configs/stm32mp157a_dk1_defconfig | 9 +++++----
> 3 files changed, 7 insertions(+), 6 deletions(-)
Patches applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-14 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 21:52 [Buildroot] [PATCH 1/2] configs/stm32mp157a_dk1: bump Linux to 6.9.8 and TF-A to 2.9 Dario Binacchi
2024-07-13 21:52 ` [Buildroot] [PATCH 2/2] configs/stm32mp157c_dk2: add hashes Dario Binacchi
2024-07-14 15:08 ` Thomas Petazzoni via buildroot [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=20240714170817.63dfd93f@windsurf \
--to=buildroot@buildroot.org \
--cc=b.bilas@grinn-global.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=marleen.vos@mind.be \
--cc=rgallaispou@gmail.com \
--cc=thomas.petazzoni@bootlin.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