public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: bruce.ashfield@gmail.com, richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/5] linux-yocto-dev: bump to v6.11
Date: Tue, 24 Sep 2024 15:01:58 +0200	[thread overview]
Message-ID: <4a44e457-b17b-41c6-8e10-18d9fbea4a88@cherry.de> (raw)
In-Reply-To: <e1eea6c3ea87aebfdaabf5a987a7290d7e9a4485.1723399246.git.bruce.ashfield@gmail.com>

Hi Bruce,

On 8/11/24 8:04 PM, Bruce Ashfield via lists.openembedded.org wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> ---
>   meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> index 0097fec7b2..292897ce43 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> @@ -14,7 +14,7 @@ require recipes-kernel/linux/linux-yocto.inc
>   # provide this .inc to set specific revisions
>   include recipes-kernel/linux/linux-yocto-dev-revisions.inc
>   
> -KBRANCH = "v6.10/standard/base"
> +KBRANCH = "v6.11/standard/base"
>   KMETA = "kernel-meta"
>   
>   SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;branch=${KBRANCH};name=machine;protocol=https \
> @@ -28,7 +28,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;branch=${KBRANCH};name
>   SRCREV_machine ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
>   SRCREV_meta ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
>   
> -LINUX_VERSION ?= "6.10"
> +LINUX_VERSION ?= "6.11"
>   LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
>   PV = "${LINUX_VERSION}+git"
>   

I haven't tried to compile linux-yocto-dev but I have my own v6.11-rc6 
based kernel recipe.

It failed to build on Scarthgap because I was missing coreutils-native 
(specifically truncate binary) because CONFIG_KALLSYMS was enabled. This 
comes from 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1472464c6248575bf2d01c7f076b94704bb32c95

It seems there are some config fragments in linux-yocto-cache 
(ktypes/base/base.cfg) with it, so maybe we want to always add the 
dependency (or is there a way to add a build time dependency from an 
.scc file?).

Is there anything I can help with?

Cheers,
Quentin


  reply	other threads:[~2024-09-24 13:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11 18:04 [PATCH 0/5] linux-yocto: consolidated pull request bruce.ashfield
2024-08-11 18:04 ` [PATCH 1/5] linux-yocto-dev: bump to v6.11 bruce.ashfield
2024-09-24 13:01   ` Quentin Schulz [this message]
2024-09-24 14:11     ` [OE-core] " Bruce Ashfield
2024-09-25 13:37       ` Quentin Schulz
2024-09-25 13:57         ` Bruce Ashfield
2024-09-25 14:06           ` Quentin Schulz
2024-09-25 14:23             ` Bruce Ashfield
2024-09-30 10:09               ` Quentin Schulz
2024-10-01 14:08                 ` Bruce Ashfield
2024-09-25 16:10         ` Ross Burton
2024-08-11 18:04 ` [PATCH 2/5] linux-yocto-rt/6.10: update to -rt14 bruce.ashfield
2024-08-11 18:04 ` [PATCH 3/5] linux-yocto/6.10: cfg: disable nfsd legacy client tracking bruce.ashfield
2024-08-11 18:04 ` [PATCH 4/5] linux-yocto/6.6: update to v6.6.44 bruce.ashfield
2024-08-11 18:04 ` [PATCH 5/5] poky/poky-tiny: bump preferred version to 6.10 bruce.ashfield
2024-08-12  9:47 ` [PATCH 0/5] linux-yocto: consolidated pull request Richard Purdie
2024-08-12 12:47   ` Bruce Ashfield

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=4a44e457-b17b-41c6-8e10-18d9fbea4a88@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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