All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Neal Frager via buildroot <buildroot@buildroot.org>
Cc: luca.ceresoli@bootlin.com, michal.simek@amd.com,
	Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v2 1/1] configs/versal_vck190_defconfig: bump to xilinx-v2023.1
Date: Tue, 8 Aug 2023 00:08:16 +0200	[thread overview]
Message-ID: <20230808000816.36f1fbea@windsurf> (raw)
In-Reply-To: <20230807055936.2343266-1-neal.frager@amd.com>

On Mon, 7 Aug 2023 06:59:36 +0100
Neal Frager via buildroot <buildroot@buildroot.org> wrote:

> This patch bumps the versal_vck190_defconfig to xilinx-v2023.1 which includes
> the following updates:
> 
> - Linux v6.1.5
> - U-Boot v2023.01
> - TF-A v2.8 (including mainline patches)
> - PLM xilinx_v2023.1
> - PSMFW xilinx_v2023.1
> - versal-firmware uses new github.com/Xilinx/soc-prebuilt-firmware repo
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>

This mixes up updating a package and a defconfig, which we normally
don't like. But admittedly this package is heavily tied to the versal
platform, so it kind of makes sense. So: applied to next. 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

      reply	other threads:[~2023-08-07 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  5:59 [Buildroot] [PATCH v2 1/1] configs/versal_vck190_defconfig: bump to xilinx-v2023.1 Neal Frager via buildroot
2023-08-07 22: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=20230808000816.36f1fbea@windsurf \
    --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.