All of lore.kernel.org
 help / color / mirror / Atom feed
From: srinuvasan.a@siemens.com
To: cip-dev@lists.cip-project.org
Cc: jan.kiszka@siemens.com, Srinuvasan A <srinuvasan.a@siemens.com>
Subject: [PATCH][isar-cip-core] recipes-initramfs/initramfs-crypt-hook: remove unwanted directory
Date: Fri, 15 Mar 2024 15:22:46 +0530	[thread overview]
Message-ID: <20240315095246.275065-1-srinuvasan.a@siemens.com> (raw)

From: Srinuvasan A <srinuvasan.a@siemens.com>

We are not installing any file under "${D}/usr/lib/encrypt_partition",
hence removed from the do_install[cleandirs] part.

Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
---
 .../initramfs-crypt-hook/initramfs-crypt-hook_0.1.bb          | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-initramfs/initramfs-crypt-hook/initramfs-crypt-hook_0.1.bb b/recipes-initramfs/initramfs-crypt-hook/initramfs-crypt-hook_0.1.bb
index 3b2e6fa..b275c0f 100644
--- a/recipes-initramfs/initramfs-crypt-hook/initramfs-crypt-hook_0.1.bb
+++ b/recipes-initramfs/initramfs-crypt-hook/initramfs-crypt-hook_0.1.bb
@@ -48,8 +48,8 @@ TEMPLATE_FILES = "encrypt_partition.env.tmpl"
 do_install[cleandirs] += " \
     ${D}/usr/share/initramfs-tools/hooks \
     ${D}/usr/share/encrypt_partition \
-    ${D}/usr/share/initramfs-tools/scripts/local-bottom \
-    ${D}/usr/lib/encrypt_partition"
+    ${D}/usr/share/initramfs-tools/scripts/local-bottom"
+
 do_install() {
     install -m 0600 "${WORKDIR}/encrypt_partition.env" "${D}/usr/share/encrypt_partition/encrypt_partition.env"
     install -m 0755 "${WORKDIR}/encrypt_partition.${CRYPT_BACKEND}.script" \
-- 
2.34.1



             reply	other threads:[~2024-03-15 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  9:52 srinuvasan.a [this message]
2024-03-15 10:00 ` [PATCH][isar-cip-core] recipes-initramfs/initramfs-crypt-hook: remove unwanted directory Jan Kiszka
2024-03-15 16:22   ` Gylstorff Quirin
2024-03-18 11:26 ` Jan Kiszka

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=20240315095246.275065-1-srinuvasan.a@siemens.com \
    --to=srinuvasan.a@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@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 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.