From: Quentin Schulz <quentin.schulz@cherry.de>
To: yocto-patches@lists.yoctoproject.org
Subject: Re: [yocto-patches] [meta-rockchip][PATCH v2 2/5] provide kernel *.inc
Date: Fri, 9 Jan 2026 11:43:49 +0100 [thread overview]
Message-ID: <6252df12-2fa4-4ad9-b1e2-e524bbce27af@cherry.de> (raw)
In-Reply-To: <20251221004843.31946-2-twoerner@gmail.com>
Hi Trevor,
On 12/21/25 1:48 AM, Trevor Woerner via lists.yoctoproject.org wrote:
[...]
> diff --git a/recipes-kernel/linux/linux-yocto-dev.bbappend b/recipes-kernel/linux/linux-yocto-dev.bbappend
> deleted file mode 100644
> index 81d2b6d693c4..000000000000
> --- a/recipes-kernel/linux/linux-yocto-dev.bbappend
> +++ /dev/null
> @@ -1,3 +0,0 @@
> -FILESEXTRAPATHS:prepend := "${THISDIR}/linux-rockchip:"
> -
> -SRC_URI:append:rockchip = " file://rockchip-kmeta;type=kmeta;name=rockchip-kmeta;destsuffix=rockchip-kmeta"
Don't you want to keep a linux-yocto-dev_%.bbappend with require
linux-rockchip.inc in there? Or would you rather not have it as to not
give ideas to people to try linux-yocto-dev instead of linux-yocto?
Cheers,
Quentin
next prev parent reply other threads:[~2026-01-09 10:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 0:48 [meta-rockchip][PATCH v2 1/5] kmeta reorganization Trevor Woerner
2025-12-21 0:48 ` [meta-rockchip][PATCH v2 2/5] provide kernel *.inc Trevor Woerner
2026-01-09 10:43 ` Quentin Schulz [this message]
2025-12-21 0:48 ` [meta-rockchip][PATCH v2 3/5] move KERNEL_FEATURES Trevor Woerner
2026-01-09 10:44 ` [yocto-patches] " Quentin Schulz
2025-12-21 0:48 ` [meta-rockchip][PATCH v2 4/5] kernel: clean up non-rockchip arch removal Trevor Woerner
2026-01-09 11:25 ` [yocto-patches] " Quentin Schulz
2025-12-21 0:48 ` [meta-rockchip][PATCH v2 5/5] fix u-boot for tf-a firmware Trevor Woerner
2026-01-09 14:09 ` [yocto-patches] " Quentin Schulz
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=6252df12-2fa4-4ad9-b1e2-e524bbce27af@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=yocto-patches@lists.yoctoproject.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 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.