From: Claudius Heine <ch@denx.de>
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [RFC PATCH 0/1] FILESEXTRAPATHS in .inc files
Date: Thu, 29 Jun 2023 15:21:07 +0200 [thread overview]
Message-ID: <20230629132107.2202204-1-ch@denx.de> (raw)
Hi,
I was writing a kernel module recipe, and I notices that I cannot
directly overwrite files that where included by modules.inc.
Isar seems to use FILESEXTRAPATHS:prepend in .inc files in multiple
places, is there a reason for it?
Attached is a RFC patch to replace FILESEXTRAPATHS:prepend with
FILESPATH:append for demonstration of what I propose.
I can do this for the other .inc files as well, but I wanted to see if I
miss something here.
regards,
Claudius
Claudius Heine (1):
linux-module: append local files path to FILSPATH
meta/recipes-kernel/linux-module/module.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.40.1
next reply other threads:[~2023-06-29 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 13:21 Claudius Heine [this message]
2023-06-29 13:21 ` [RFC PATCH 1/1] linux-module: append local files path to FILSPATH Claudius Heine
2023-06-29 13:43 ` Claudius Heine
2023-06-30 11:36 ` Kanagarajan, Vijaikumar
2023-07-04 7:51 ` Claudius Heine
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=20230629132107.2202204-1-ch@denx.de \
--to=ch@denx.de \
--cc=isar-users@googlegroups.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