From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: michal.simek@amd.com, thomas.petazzoni@bootlin.com,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 2/3] configs/zynqmp_zcu106_defconfig: bump to Xilinx 2022.2
Date: Thu, 1 Dec 2022 09:38:41 +0100 [thread overview]
Message-ID: <20221201093841.7d21d5c9@booty> (raw)
In-Reply-To: <20221126105350.14687-2-neal.frager@amd.com>
On Sat, 26 Nov 2022 03:53:49 -0700
Neal Frager <neal.frager@amd.com> wrote:
> This patch bumps the zynqmp_zcu106_defconfig to Xilinx release 2022.2.
>
> Xilinx 2022.2 includes:
> - U-Boot 2022.01 bug fixes
> - Linux bump to Linux 5.15.36 with bug fixes
> - TF-A 2.6 bug fixes
> - PMUFW bug fixes
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-01 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 10:53 [Buildroot] [PATCH v1 1/3] configs/zynqmp_zcu102_defconfig: bump to Xilinx 2022.2 Neal Frager via buildroot
2022-11-26 10:53 ` [Buildroot] [PATCH v1 2/3] configs/zynqmp_zcu106_defconfig: " Neal Frager via buildroot
2022-12-01 8:38 ` Luca Ceresoli via buildroot [this message]
2022-12-02 18:50 ` Peter Korsgaard
2022-11-26 10:53 ` [Buildroot] [PATCH v1 3/3] configs/zynqmp_kria_kv260_defconfig: " Neal Frager via buildroot
2022-12-01 8:39 ` Luca Ceresoli via buildroot
2022-12-02 18:51 ` Peter Korsgaard
2022-11-29 10:50 ` [Buildroot] [PATCH v1 1/3] configs/zynqmp_zcu102_defconfig: " Luca Ceresoli via buildroot
2022-11-29 11:11 ` Frager, Neal via buildroot
2022-12-01 8:38 ` Luca Ceresoli via buildroot
2022-12-02 18:50 ` 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=20221201093841.7d21d5c9@booty \
--to=buildroot@buildroot.org \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.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 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.