From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: ju.o@free.fr, buildroot@buildroot.org,
giulio.benetti@benettiengineering.com, michal.simek@amd.com
Subject: Re: [Buildroot] [PATCH v1 1/3] configs/zynq_zc706_defconfig: bump to Xilinx 2022.2
Date: Wed, 9 Nov 2022 16:45:03 +0100 [thread overview]
Message-ID: <20221109164503.1ca7755c@booty> (raw)
In-Reply-To: <20221019051823.26706-1-neal.frager@amd.com>
Hi Neal,
apologies for the delay, I had missed these patches.
On Tue, 18 Oct 2022 23:18:21 -0600
Neal Frager <neal.frager@amd.com> wrote:
> This patch bumps the zc706 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
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
So let's upgrate to 2022.2 before the new year comes! :)
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-11-09 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 5:18 [Buildroot] [PATCH v1 1/3] configs/zynq_zc706_defconfig: bump to Xilinx 2022.2 Neal Frager via buildroot
2022-10-19 5:18 ` [Buildroot] [PATCH v1 2/3] configs/zynq_microzed_defconfig: " Neal Frager via buildroot
2022-11-09 15:45 ` Luca Ceresoli via buildroot
2022-10-19 5:18 ` [Buildroot] [PATCH v1 3/3] configs/zynq_zed_defconfig: " Neal Frager via buildroot
2022-11-09 15:45 ` Luca Ceresoli via buildroot
2022-11-08 5:11 ` [Buildroot] [PATCH v1 1/3] configs/zynq_zc706_defconfig: " Frager, Neal via buildroot
2022-11-09 15:45 ` Luca Ceresoli via buildroot [this message]
2022-11-09 22:05 ` Thomas Petazzoni via buildroot
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=20221109164503.1ca7755c@booty \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=ju.o@free.fr \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.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.