This series moves RISC-V specific configuration out of linux-yocto.inc into a
new inc file: linux-yocto-features.inc.

By relocating these RISC-V specific settings, the configuration remains
available for oe-core builds while avoiding unintended side effects for external
or custom recipes that require such include file.

The first patch only changes u-boot, and u-boot contains only one versioned
recipe, so I kept it as it was in v1.

Changes in v2:
- As per the comments in v1, I created a new inc file that is now included in
  the versioned recipes

João Marcos Costa (2):
  u-boot: relocate SRC_URI_RISCV into recipe
  linux-yocto: relocate KERNEL_FEATURES_RISCV

 meta/recipes-bsp/u-boot/u-boot-common.inc        | 12 ------------
 meta/recipes-bsp/u-boot/u-boot_2025.10.bb        | 12 ++++++++++++
 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 +
 14 files changed, 37 insertions(+), 28 deletions(-)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-features.inc

-- 
2.47.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#229004): 
https://lists.openembedded.org/g/openembedded-core/message/229004
Mute This Topic: https://lists.openembedded.org/mt/117135530/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to