public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Joao Marcos Costa <joaomarcos.costa@bootlin.com>
To: openembedded-core@lists.openembedded.org
Cc: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	Khem Raj <raj.khem@gmail.com>, Ross Burton <ross.burton@arm.com>,
	"antonin.godard@bootlin.com" <antonin.godard@bootlin.com>
Subject: Re: [PATCH v2 2/2] linux-yocto: relocate KERNEL_FEATURES_RISCV
Date: Tue, 10 Feb 2026 10:05:07 +0100	[thread overview]
Message-ID: <9a9d7324-dbf0-4fd5-991f-311057f12237@bootlin.com> (raw)
In-Reply-To: <20260107151436.964819-3-joaomarcos.costa@bootlin.com>

Hello,

I hope this email finds you well.

On 1/7/26 16:14, João Marcos Costa wrote:
> In a custom linux recipe that requires linux-yocto.inc, the metadata
> files (*.scc) end up in KERNEL_FEATURES. However, the custom recipe's
> FILESPATH does not contain the path to oe-core's linux-yocto directory
> (as expected), which leads to the error below:
> 
> ERROR: linux-custom-6.12.15+git-r0 do_kernel_metadata:
> Feature 'arch/riscv/tunes/riscv-isa-clear.scc' not found, this will cause configuration failures.
> ERROR: linux-custom-6.12.15+git-r0 do_kernel_metadata:
> Check the SRC_URI for meta-data repositories or directories that may be missing
> 
> Move KERNEL_FEATURES_RISCV - along with the appends - to a new file:
> linux-yocto-features.inc.
> 
> Signed-off-by: João Marcos Costa <joaomarcos.costa@bootlin.com>
> ---
>   meta/recipes-kernel/linux/linux-yocto-dev.bb     |  1 +
>   .../linux/linux-yocto-features.inc               | 15 +++++++++++++++
>   meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb |  1 +
>   meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb |  1 +
>   meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb |  1 +
>   .../linux/linux-yocto-tiny_6.12.bb               |  1 +
>   .../linux/linux-yocto-tiny_6.16.bb               |  1 +
>   .../linux/linux-yocto-tiny_6.18.bb               |  1 +
>   meta/recipes-kernel/linux/linux-yocto.inc        | 16 ----------------
>   meta/recipes-kernel/linux/linux-yocto_6.12.bb    |  1 +
>   meta/recipes-kernel/linux/linux-yocto_6.16.bb    |  1 +
>   meta/recipes-kernel/linux/linux-yocto_6.18.bb    |  1 +
>   12 files changed, 25 insertions(+), 16 deletions(-)
>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-features.inc
> 
(...)

I just saw that the previous patch (same fix, but in u-boot) made its 
way into oe-core/master, but this linux-yocto patch here didn't.

Would you have any feedbacks about it? Something to be 
reworked/rephrased, otherwise I'd say this patch is needed just as much 
as the u-boot one.

Also, my original intent was to provide a fix a problem I faced in 
Whinlatter, so backporting those patches should be needed as well. I 
will work on it, of course, but I'd like first to make sure the 
linux-yocto patch is not left outside.

Thanks!
-- 
Best regards,
João Marcos Costa


  reply	other threads:[~2026-02-10  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 15:14 [PATCH v2 0/2] Move RISC-V recipe-specific configuration out of common includes João Marcos Costa
2026-01-07 15:14 ` [PATCH v2 1/2] u-boot: relocate SRC_URI_RISCV into recipe João Marcos Costa
2026-01-07 15:14 ` [PATCH v2 2/2] linux-yocto: relocate KERNEL_FEATURES_RISCV João Marcos Costa
2026-02-10  9:05   ` Joao Marcos Costa [this message]
2026-01-14 10:01 ` [PATCH v2 0/2] Move RISC-V recipe-specific configuration out of common includes Joao Marcos Costa
2026-01-14 12:30   ` [OE-core] " Richard Purdie
2026-01-14 12:34     ` Joao Marcos Costa

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=9a9d7324-dbf0-4fd5-991f-311057f12237@bootlin.com \
    --to=joaomarcos.costa@bootlin.com \
    --cc=antonin.godard@bootlin.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@arm.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