All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinuvasan Arjunan <srinuvasan_a@mentor.com>
To: <cip-dev@lists.cip-project.org>
Cc: <jan.kiszka@siemens.com>, Srinuvasan A <srinuvasan.a@siemens.com>
Subject: [PATCH][isar-cip-core] secure-boot-secrets/files: remove unwanted link files
Date: Thu, 7 Sep 2023 18:21:48 +0530	[thread overview]
Message-ID: <20230907125148.10628-1-srinuvasan_a@mentor.com> (raw)

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

We have soft link for all the codename to fetch the keys, observed some
unwanted link file available in buster folder, hence remove them.

Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
---
 recipes-devtools/secure-boot-secrets/files/buster/bookworm | 1 -
 recipes-devtools/secure-boot-secrets/files/buster/bullseye | 1 -
 2 files changed, 2 deletions(-)
 delete mode 120000 recipes-devtools/secure-boot-secrets/files/buster/bookworm
 delete mode 120000 recipes-devtools/secure-boot-secrets/files/buster/bullseye

diff --git a/recipes-devtools/secure-boot-secrets/files/buster/bookworm b/recipes-devtools/secure-boot-secrets/files/buster/bookworm
deleted file mode 120000
index b7dbeb4..0000000
--- a/recipes-devtools/secure-boot-secrets/files/buster/bookworm
+++ /dev/null
@@ -1 +0,0 @@
-../../secure-boot-secrets/files/bookworm
\ No newline at end of file
diff --git a/recipes-devtools/secure-boot-secrets/files/buster/bullseye b/recipes-devtools/secure-boot-secrets/files/buster/bullseye
deleted file mode 120000
index 3c7fe4f..0000000
--- a/recipes-devtools/secure-boot-secrets/files/buster/bullseye
+++ /dev/null
@@ -1 +0,0 @@
-../../secure-boot-secrets/files/bullseye
\ No newline at end of file
-- 
2.34.1



             reply	other threads:[~2023-09-07 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 12:51 Srinuvasan Arjunan [this message]
2023-09-07 12:57 ` [PATCH][isar-cip-core] secure-boot-secrets/files: remove unwanted link files 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=20230907125148.10628-1-srinuvasan_a@mentor.com \
    --to=srinuvasan_a@mentor.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@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 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.