From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 5/9] kern-tools: fix queue processing in relative TOPDIR configurations
Date: Mon, 19 Sep 2022 10:28:30 -0400 [thread overview]
Message-ID: <78ed9d2a9349ad9db6d98bf8f5c76a332e025bf4.1663597409.git.bruce.ashfield@gmail.com> (raw)
In-Reply-To: <cover.1663597409.git.bruce.ashfield@gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
As reported by Peter Hoyes, in some very specific configurations
the processing done by the kern-tools results in errors. This is
due to the bad creation of relative paths to patches and configuration.
This is fixed by the following kern-tools commit (based on a similar
suggestion by Peter):
spp: ensure that relocations and patch paths are absolute
If include directories (locations of layers) have relative
components, and the path to a patch doesn't share that relative
location, the detection of a common prefix can fail.
When the common prefix is incorrectly specified, it can be the
entire path to a patch. This results in everything being removed
and subtle errors (as this shouldn't happen).
By ensuring that both the relocation directories and patch path
are absolute, we can avoid this issue.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 11613ab3b6..e065c3e74f 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "\
DEPENDS = "git-native"
-SRCREV = "f70b1d52f4706a263ae22e2c61039ccd875e97b6"
+SRCREV = "9320c2a1aaa085e94abd15ede0d93ffdab578e9d"
PV = "0.3+git${SRCPV}"
inherit native
--
2.19.1
next prev parent reply other threads:[~2022-09-19 14:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 14:28 [PATCH 0/9] kernel-yocto: consolidated pull request bruce.ashfield
2022-09-19 14:28 ` [PATCH 1/9] linux-yocto/5.15: update to v5.15.63 bruce.ashfield
2022-09-19 14:28 ` [PATCH 2/9] linux-yocto/5.19: update to v5.19.5 bruce.ashfield
2022-09-19 14:28 ` [PATCH 3/9] linux-yocto/5.19: update to v5.19.7 bruce.ashfield
2022-09-19 14:28 ` [PATCH 4/9] linux-yocto/5.15: update to v5.15.65 bruce.ashfield
2022-09-19 14:28 ` bruce.ashfield [this message]
2022-09-19 14:28 ` [PATCH 6/9] linux-yocto: Enable mdio for qemu bruce.ashfield
2022-09-19 14:28 ` [PATCH 7/9] kern-tools: allow 'y' or 'm' to avoid config audit warnings bruce.ashfield
2022-09-19 14:28 ` [PATCH 8/9] linux-yocto/5.19: update to v5.19.9 bruce.ashfield
2022-09-19 14:28 ` [PATCH 9/9] linux-yocto/5.15: update to v5.15.68 bruce.ashfield
2022-09-23 21:31 ` [OE-core] " Steve Sakoman
2022-09-24 2:21 ` Bruce Ashfield
2022-09-24 2:32 ` Steve Sakoman
2022-09-19 21:23 ` [OE-core] [PATCH 0/9] kernel-yocto: consolidated pull request Khem Raj
2022-09-20 9:45 ` Richard Purdie
2022-09-20 12:21 ` Richard Purdie
2022-09-20 12:53 ` Bruce Ashfield
2022-09-20 12:55 ` Richard Purdie
2022-09-20 20:29 ` 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=78ed9d2a9349ad9db6d98bf8f5c76a332e025bf4.1663597409.git.bruce.ashfield@gmail.com \
--to=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