From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Clément Péron" <peron.clem@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 2/2] configs/beelink_gs1: bump to linux 5.15, atf 2.5 and u-boot 2021.10
Date: Sun, 30 Jan 2022 18:16:59 +0100 [thread overview]
Message-ID: <20220130181659.1e3aae5a@windsurf> (raw)
In-Reply-To: <20220129111731.736265-2-peron.clem@gmail.com>
On Sat, 29 Jan 2022 12:17:31 +0100
Clément Péron <peron.clem@gmail.com> wrote:
> U-boot libfdt fails to compile on CI.
> /usr/bin/ld: scripts/dtc/dtc-parser.tab.o:(.bss+0x10): multiple definition of `yylloc'; scripts/dtc/dtc-lexer.lex.o:(.bss+0x0): first defined here
> collect2: error: ld returned 1 exit status
>
> https://gitlab.com/buildroot.org/buildroot/-/jobs/2021478208
>
> As this fix has been already upstreamed just bump U-boot package.
>
> Let's also bump Kernel and ATF as the board is properly supported upstream.
>
> Signed-off-by: Clément Péron <peron.clem@gmail.com>
> ---
> configs/beelink_gs1_defconfig | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
Applied to master, 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-01-30 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 11:17 [Buildroot] [PATCH v2 1/2] configs/beelink_gs1: increase rootfs size to 120M Clément Péron
2022-01-29 11:17 ` [Buildroot] [PATCH v2 2/2] configs/beelink_gs1: bump to linux 5.15, atf 2.5 and u-boot 2021.10 Clément Péron
2022-01-29 11:22 ` Giulio Benetti
2022-01-30 17:16 ` Thomas Petazzoni via buildroot [this message]
2022-01-30 17:18 ` [Buildroot] [PATCH v2 1/2] configs/beelink_gs1: increase rootfs size to 120M Thomas Petazzoni via buildroot
2022-01-31 12:43 ` Clément Péron
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=20220130181659.1e3aae5a@windsurf \
--to=buildroot@buildroot.org \
--cc=peron.clem@gmail.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