From: "srinuvasan.a via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: cedric.hombourger@siemens.com, srinuvasan <srinuvasan.a@siemens.com>
Subject: [PATCH v1 1/2] meta/recipes-kernel/linux: correct the kernel header dir name
Date: Mon, 14 Oct 2024 20:54:39 +0530 [thread overview]
Message-ID: <20241014152440.1310394-1-srinuvasan.a@siemens.com> (raw)
From: srinuvasan <srinuvasan.a@siemens.com>
Presently kernel headers packages not cleaned in the do_clean stage
of kernel build process, this is due to we are referring wrong directory name
during clean stage.
Updated the correct dir name as "deb_kern_hdr_dir".
Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
---
meta/recipes-kernel/linux/files/debian/isar/clean.tmpl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux/files/debian/isar/clean.tmpl b/meta/recipes-kernel/linux/files/debian/isar/clean.tmpl
index bc67595b..8cceb6e2 100644
--- a/meta/recipes-kernel/linux/files/debian/isar/clean.tmpl
+++ b/meta/recipes-kernel/linux/files/debian/isar/clean.tmpl
@@ -11,7 +11,7 @@ do_clean() {
set -x
rm -rf ${deb_img_dir} ${deb_dbg_dir}
- rm -rf ${deb_kern_hdrdir}
+ rm -rf ${deb_kern_hdr_dir}
rm -rf ${deb_libc_hdr_dir}
# Stop tracing
--
2.39.5
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20241014152440.1310394-1-srinuvasan.a%40siemens.com.
next reply other threads:[~2024-10-14 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 15:24 srinuvasan.a via isar-users [this message]
2024-10-14 15:24 ` [PATCH v1 2/2] meta/recipes-kernel/linux: add additional directory for cleanup srinuvasan.a via isar-users
2024-10-21 10:51 ` [PATCH v1 1/2] meta/recipes-kernel/linux: correct the kernel header dir name Uladzimir Bely
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=20241014152440.1310394-1-srinuvasan.a@siemens.com \
--to=isar-users@googlegroups.com \
--cc=cedric.hombourger@siemens.com \
--cc=srinuvasan.a@siemens.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