All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] configs/qemu_riscv64_virt: Update to 5.1 kernel
Date: Wed, 19 Jun 2019 07:29:46 +0200	[thread overview]
Message-ID: <20190619072946.18056b53@windsurf> (raw)
In-Reply-To: <20190618235358.10613-1-alistair.francis@wdc.com>

Hello Alistair,

On Tue, 18 Jun 2019 16:53:57 -0700
Alistair Francis <alistair.francis@wdc.com> wrote:

> Update the 64-bit defconfig to use the latest kernel.
> 
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> ---
>  configs/qemu_riscv64_virt_defconfig | 5 -----
>  1 file changed, 5 deletions(-)
> 
> diff --git a/configs/qemu_riscv64_virt_defconfig b/configs/qemu_riscv64_virt_defconfig
> index 12afac44fb..e2932778ec 100644
> --- a/configs/qemu_riscv64_virt_defconfig
> +++ b/configs/qemu_riscv64_virt_defconfig
> @@ -10,13 +10,8 @@ BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
>  # Filesystem
>  BR2_TARGET_ROOTFS_EXT2=y
>  
> -# Linux headers same as kernel, a 4.20 series
> -BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_20=y
> -
>  # Kernel
>  BR2_LINUX_KERNEL=y
> -BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.20.17"

You need to keep an explicit Linux kernel version, both for the kernel
itself and the headers. Indeed, we don't want defconfigs to
automatically "move" to a newer kernel version when it gets added in
Buildroot, as we want the defconfigs to be known-working references.

Could you adjust this in this patch and the second patch as well ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2019-06-19  5:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 23:53 [Buildroot] [PATCH 1/2] configs/qemu_riscv64_virt: Update to 5.1 kernel Alistair Francis
2019-06-18 23:53 ` [Buildroot] [PATCH 2/2] configs/qemu_riscv32_virt: " Alistair Francis
2019-06-19  5:29 ` Thomas Petazzoni [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=20190619072946.18056b53@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.