From: Romain Naour <romain.naour@gmail.com>
To: Peter Korsgaard <peter@korsgaard.com>, buildroot@buildroot.org
Cc: Gerome Burlats <gerome.burlats@smile.fr>
Subject: Re: [Buildroot] [PATCH 3/3] configs/qemu_aarch64_virt_defconfig: bump Linux kernel to 5.15.16
Date: Sun, 23 Jan 2022 11:56:39 +0100 [thread overview]
Message-ID: <bde7ae07-e97b-592a-1680-da61af531fe8@gmail.com> (raw)
In-Reply-To: <20220122153714.26991-3-peter@korsgaard.com>
Hello Peter, All
Le 22/01/2022 à 16:37, Peter Korsgaard a écrit :
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> configs/qemu_aarch64_virt_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configs/qemu_aarch64_virt_defconfig b/configs/qemu_aarch64_virt_defconfig
> index 0caf38112d..9fbf293311 100644
> --- a/configs/qemu_aarch64_virt_defconfig
> +++ b/configs/qemu_aarch64_virt_defconfig
> @@ -20,7 +20,7 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_15=y
> # Kernel
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.15"
> +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.15.16"
Why just only taking care of this defconfig ?
Most qemu defconfig are using the same kernel version (5.15). Usually we try to
keep all of them in sync.
Since Qemu defconfigs are runtime tested each week in GitLab-CI maybe we can
safely switch to BR2_LINUX_KERNEL_LATEST_VERSION instead ?
But we have to check qemu defconfigs using a local kernel patch, currently
ppc-mpc8544ds and arm-versatile or keeping kernel custom version for them.
Also BR2_LINUX_KERNEL_LATEST_VERSION refer to the latest stable kernel version,
not the latest lts version.
Thoughts?
Best regards,
Romain
> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/aarch64-virt/linux.config"
> BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-23 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 15:37 [Buildroot] [PATCH 1/3] configs/qemu_aarch64_virt_defconfig: don't hard code getty port Peter Korsgaard
2022-01-22 15:37 ` [Buildroot] [PATCH 2/3] configs/qemu_aarch64_virt_defconfig: linux.config: enable fb/input support Peter Korsgaard
2022-01-22 15:37 ` [Buildroot] [PATCH 3/3] configs/qemu_aarch64_virt_defconfig: bump Linux kernel to 5.15.16 Peter Korsgaard
2022-01-23 10:56 ` Romain Naour [this message]
2022-01-23 14:48 ` Peter Korsgaard
2022-01-23 15:48 ` Romain Naour
2022-01-22 19:10 ` [Buildroot] [PATCH 1/3] configs/qemu_aarch64_virt_defconfig: don't hard code getty port Yann E. MORIN
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=bde7ae07-e97b-592a-1680-da61af531fe8@gmail.com \
--to=romain.naour@gmail.com \
--cc=buildroot@buildroot.org \
--cc=gerome.burlats@smile.fr \
--cc=peter@korsgaard.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