Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: Neal Frager <neal.frager@amd.com>, buildroot@buildroot.org
Cc: giulio.benetti@benettiengineering.com
Subject: Re: [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: bump to Xilinx 2022.1
Date: Tue, 3 May 2022 15:33:02 +0200	[thread overview]
Message-ID: <fa3f0b8e-ff8a-d682-9b65-4811986d0e23@lucaceresoli.net> (raw)
In-Reply-To: <20220502074907.3941472-2-neal.frager@amd.com>

Hi,

On 02/05/22 09:49, Neal Frager wrote:
> This patch bumps configs/zynqmp_zcu106_defconfig to Xilinx software release 2022.1
> which includes the following updates:
>   - TF-A release version 2.6
>   - U-Boot release version 2022.01
>   - Linux kernel release version 5.15.19
> 
> It is better to use a Xilinx official release version than sha tags.
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>

Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net>


-- 
Luca
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-05-03 13:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02  7:49 [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: bump to Xilinx 2022.1 Neal Frager via buildroot
2022-05-02  7:49 ` [Buildroot] [PATCH v1 2/2] configs/zynqmp_zcu106_defconfig: " Neal Frager via buildroot
2022-05-03 13:32   ` Luca Ceresoli
2022-05-03 13:33   ` Luca Ceresoli [this message]
2022-05-03 14:17   ` Peter Korsgaard
2022-05-28  6:58   ` Peter Korsgaard
2022-05-03 14:17 ` [Buildroot] [PATCH v1 1/2] configs/zynqmp_zcu102_defconfig: " Peter Korsgaard
2022-05-03 14:38   ` Neal Frager
2022-05-03 14:44     ` Peter Korsgaard
2022-05-28  6:58 ` 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=fa3f0b8e-ff8a-d682-9b65-4811986d0e23@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox