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 v1 1/2] board/zynqmp/zcu106/patches: remove patch
Date: Sun, 11 Dec 2022 17:55:59 +0100 [thread overview]
Message-ID: <20221211175559.73447189@windsurf> (raw)
In-Reply-To: <20221207122133.14860-1-neal.frager@amd.com>
Hello Neal,
On Wed, 7 Dec 2022 05:21:32 -0700
Neal Frager via buildroot <buildroot@buildroot.org> wrote:
> The 0001-arm64-zynqmp-zynqmp-zcu106-revA-Fix-DP-PLL-configura.patch
> is already committed in the Xilinx 2022.2 u-boot release tag.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
> ...qmp-zcu102-revA-Fix-DP-PLL-configura.patch | 40 -------------------
> configs/zynqmp_zcu106_defconfig | 1 -
> 2 files changed, 41 deletions(-)
> delete mode 100644 board/zynqmp/zcu106/patches/uboot/0001-arm64-zynqmp-zynqmp-zcu102-revA-Fix-DP-PLL-configura.patch
This should have been part of the commit updating U-Boot. If you didn't
notice then, then this commit should have been very different: (1) it
should clearly indicate that it fixes a bug and (2) it should point to
the commit it is fixing. I've committed with the following commit log:
board/zynqmp/zcu106/patches: fix build by dropping U-Boot patch
Since commit
3c997c457a4ee33d81e6b93e4f6f147bb9e861e9 ("configs/zynqmp_zcu106_defconfig:
bump to Xilinx 2022.2"), we're using U-Boot version Xilinx 2022.2,
which already carries the psu_init_gpl.c, causing the build to fail as
our patch doesn't apply.
Fix this by dropping the no longer needed patch.
Fixes: 3c997c457a4ee33d81e6b93e4f6f147bb9e861e9 ("configs/zynqmp_zcu106_defconfig: bump to Xilinx 2022.2")
Signed-off-by: Neal Frager <neal.frager@amd.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
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
next prev parent reply other threads:[~2022-12-11 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 12:21 [Buildroot] [PATCH v1 1/2] board/zynqmp/zcu106/patches: remove patch Neal Frager via buildroot
2022-12-07 12:21 ` [Buildroot] [PATCH v1 2/2] board/zynqmp/kria/patches: " Neal Frager via buildroot
2022-12-11 16:58 ` Thomas Petazzoni via buildroot
2022-12-21 15:54 ` Peter Korsgaard
2022-12-11 16:55 ` Thomas Petazzoni via buildroot [this message]
2022-12-21 15:53 ` [Buildroot] [PATCH v1 1/2] board/zynqmp/zcu106/patches: " 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=20221211175559.73447189@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.