From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Romain Naour <romain.naour@smile.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] support/testing: fs: f2fs: bump test Kernel to 6.6.27
Date: Wed, 1 May 2024 23:31:27 +0200 [thread overview]
Message-ID: <20240501233127.78a845c8@windsurf> (raw)
In-Reply-To: <20240415193522.7719-1-ju.o@free.fr>
On Mon, 15 Apr 2024 21:35:22 +0200
Julien Olivain <ju.o@free.fr> wrote:
> Since the toolchain Bootlin update to 2023.11-1 [1], the arm Linux
> kernel build is broken with binutils >= 2.41 with:
>
> arch/arm/mm/proc-v7.S: Assembler messages:
> arch/arm/mm/proc-v7.S:640: Error: junk at end of line, first unrecognized character is '#'
>
> This commit fixes the issue by bumping the test Kernel version to the
> latest LTS version 6.6.27. We bump to the 6.6.x series to refresh the
> test, as the 4.19.x series is planned to be end-of-life soon, in
> December 2024.
>
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/6623401447
>
> [1] https://gitlab.com/buildroot.org/buildroot/-/commit/7e0e6e3b8618ab942f25b11ee72fbc5a4deefdf1
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> support/testing/tests/fs/test_f2fs.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master after rebasing, and adjusting the commit message as
the change is no longer fixing the build, it was already done by Romain
Naour.
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
prev parent reply other threads:[~2024-05-01 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 19:35 [Buildroot] [PATCH 1/1] support/testing: fs: f2fs: bump test Kernel to 6.6.27 Julien Olivain
2024-04-30 21:54 ` Romain Naour
2024-05-01 21:31 ` 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=20240501233127.78a845c8@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=romain.naour@smile.fr \
--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