From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/6] configs/mender_x86_64_efi_defconfig: Update kernel to latest LTS version
Date: Tue, 19 Dec 2023 17:08:13 +0100 [thread overview]
Message-ID: <20231219170813.581a2065@windsurf> (raw)
In-Reply-To: <20231218212613.1201821-1-adam.duskett@amarulasolutions.com>
On Mon, 18 Dec 2023 14:26:08 -0700
Adam Duskett <adam.duskett@amarulasolutions.com> wrote:
> 5.18 is not a LTS version. Let's update the kernel to use the LTS 6.1 kernel.
>
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
> ---
> v1 -> v2: Bump kernel version from 6.1.58 to 6.1.68
>
> configs/mender_x86_64_efi_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configs/mender_x86_64_efi_defconfig b/configs/mender_x86_64_efi_defconfig
> index 25a463abb3..260cd8a1e2 100644
> --- a/configs/mender_x86_64_efi_defconfig
> +++ b/configs/mender_x86_64_efi_defconfig
> @@ -39,7 +39,7 @@ BR2_ROOTFS_POST_SCRIPT_ARGS="--data-part-size=32M --device-type=buildroot-x86_64
> # Kernel
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.18.14"
> +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.1.68"
You probably also want to change:
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_18=y
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-12-19 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 21:26 [Buildroot] [PATCH v2 1/6] configs/mender_x86_64_efi_defconfig: Update kernel to latest LTS version Adam Duskett
2023-12-18 21:26 ` [Buildroot] [PATCH v2 2/6] package/mender-grubenv: Fix per-package building Adam Duskett
2023-12-18 21:26 ` [Buildroot] [PATCH v2 3/6] package/mender-grubenv: bump version to 64e32b01d1bf54784d2a290ad0469c583e843864 Adam Duskett
2023-12-18 21:26 ` [Buildroot] [PATCH v2 4/6] package/mender-artifact: bump version to 3.10.2 Adam Duskett
2023-12-18 21:26 ` [Buildroot] [PATCH v2 5/6] package/mender-connect: bump version to 2.1.1 Adam Duskett
2023-12-18 21:26 ` [Buildroot] [PATCH v2 6/6] package/mender: bump version to 3.5.1 Adam Duskett
2023-12-19 16:08 ` 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=20231219170813.581a2065@windsurf \
--to=buildroot@buildroot.org \
--cc=adam.duskett@amarulasolutions.com \
--cc=angelo.compagnucci@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