From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [git commit] configs/ci20_defconfig: bump to kernel 5.4.254
Date: Wed, 13 Sep 2023 09:00:00 +0200 [thread overview]
Message-ID: <87wmwu4ky7.fsf@48ers.dk> (raw)
In-Reply-To: <20230820214028.0B1A385EF6@busybox.osuosl.org> (Thomas Petazzoni via buildroot's message of "Sun, 20 Aug 2023 23:38:51 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=486a3ba4c3a78668eee1dd4f4b312a75a1b029c5
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> Bump the kernel to the latest release of 5.4 kernel series
> to fix an issue with gcc 12.
> arch/mips/jz4740/setup.c: In function 'plat_mem_setup':
> arch/mips/jz4740/setup.c:64:25: error: comparison between two arrays [-Werror=array-compare]
> 64 | if (__dtb_start != __dtb_end)
> | ^~
> arch/mips/jz4740/setup.c:64:25: note: use '&__dtb_start[0] != &__dtb_end[0]' to compare the addresses
> CC fs/debugfs/file.o
> cc1: all warnings being treated as errors
> Fixed in v5.4.195:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a60def7568216684f62b117c199429c4a9a89570
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/4889436573
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to 2023.02.x and 2023.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-13 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 21:38 [Buildroot] [git commit] configs/ci20_defconfig: bump to kernel 5.4.254 Thomas Petazzoni via buildroot
2023-09-13 7:00 ` Peter Korsgaard [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=87wmwu4ky7.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--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