From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/7] support/testing: test_xfsprogs: use bootlin toolchain, update kernel
Date: Fri, 20 Mar 2026 16:54:48 +0100 [thread overview]
Message-ID: <20260320155448.176144-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260313215044.2406044-1-ju.o@free.fr>
In reply of:
> This commit updates the test configuration to switch to a Bootlin
> external toolchain. This is needed to get newer toolchain kernel
> headers required by newer xfsprogs versions.
>
> xfsprogs upstream commit [1] (included in v6.15) introduced a usage
> of the "capacity" field of zoned block devices, introduced in Kernel
> commit [2], first included in v5.9.
>
> This commit also updates the runtime test Kernel version
> to the LTS 6.18.18. This is because the default filesystem options
> of mkfs.xfs were updated in upstream commit [3] to include new
> features supported in the new Kernel 6.18.y LTS series. The commit [3]
> is included in xfsprogs v6.18.
>
> [1] https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=48ccc2459039309cfbaf358febea53a86f07827c
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=82394db7383d33641f3f565bd79792fb41b1741f
> [3] https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=54aad16b4b9b923442b4042afaba4438ca1aa868
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
Applied to 2026.02.x. Thanks
> ---
> Changes:
> v1-> v2:
> - new patch, separated from the xfsprogs bump in v1
> - kernel updated from 6.18.9 to 6.18.18
> ---
> support/testing/tests/package/test_xfsprogs.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/support/testing/tests/package/test_xfsprogs.py b/support/testing/tests/package/test_xfsprogs.py
> index a3a4bd27d8..03191aa22b 100644
> --- a/support/testing/tests/package/test_xfsprogs.py
> +++ b/support/testing/tests/package/test_xfsprogs.py
> @@ -12,10 +12,11 @@ class TestXfsProgs(infra.basetest.BRTest):
> f"""
> BR2_aarch64=y
> BR2_TOOLCHAIN_EXTERNAL=y
> + BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
> BR2_TARGET_GENERIC_GETTY_PORT="ttyAMA0"
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> - BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.6.37"
> + BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.18"
> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/aarch64-virt/linux.config"
> BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="{kern_frag}"
> --
> 2.53.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-03-20 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 21:50 [Buildroot] [PATCH v2 1/7] support/testing: test_xfsprogs: use bootlin toolchain, update kernel Julien Olivain via buildroot
2026-03-13 21:50 ` [Buildroot] [PATCH v2 2/7] package/xfsprogs: bump version to 6.18.0 Julien Olivain via buildroot
2026-03-13 21:50 ` [Buildroot] [PATCH v2 3/7] package/inih: enable host package variant Julien Olivain via buildroot
2026-03-13 21:50 ` [Buildroot] [PATCH v2 4/7] package/liburcu: " Julien Olivain via buildroot
2026-03-13 21:50 ` [Buildroot] [PATCH v2 5/7] package/xfsprogs: " Julien Olivain via buildroot
2026-03-13 21:50 ` [Buildroot] [PATCH v2 6/7] fs/xfs: add support for generating a xfs image Julien Olivain via buildroot
2026-03-13 21:50 ` [Buildroot] [PATCH v2 7/7] support/testing: fs: new xfs runtime test Julien Olivain via buildroot
2026-03-13 22:50 ` [Buildroot] [PATCH v2 1/7] support/testing: test_xfsprogs: use bootlin toolchain, update kernel Romain Naour via buildroot
2026-03-20 15:54 ` Thomas Perale 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=20260320155448.176144-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.perale@mind.be \
/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