From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <neal.frager@amd.com>
Cc: michal.simek@amd.com, luca.ceresoli@bootlin.com,
thomas.petazzoni@bootlin.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/3] configs/zynqmp_zcu102_defconfig: bump to Xilinx 2022.2
Date: Fri, 02 Dec 2022 19:50:50 +0100 [thread overview]
Message-ID: <87wn798ws5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221126105350.14687-1-neal.frager@amd.com> (Neal Frager's message of "Sat, 26 Nov 2022 03:53:48 -0700")
>>>>> "Neal" == Neal Frager <neal.frager@amd.com> writes:
> This patch bumps the zynqmp_zcu102_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>
We're a bit late for 2022.11, but ok.
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-12-02 18:50 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
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 [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=87wn798ws5.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox