From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: "Su, Bao Cheng (RC-CN DF FA R&D)" <baocheng.su@siemens.com>
Subject: Re: [PATCH] optee-client: Escape the escape sequence in tee-supplicant.service
Date: Thu, 20 Jul 2023 18:25:30 +0200 [thread overview]
Message-ID: <8f6cd1f7-b263-94ee-d909-4c61ecb3a5e4@siemens.com> (raw)
In-Reply-To: <0bf7882b-0f78-d2d0-1a33-39c437bfbb7e@siemens.com>
On 17.07.23 13:24, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Resolves "Ignoring unknown escape sequences" warnings and ensure proper
> module unloading.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> .../optee-client/files/debian/tee-supplicant.service | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-bsp/optee-client/files/debian/tee-supplicant.service b/meta/recipes-bsp/optee-client/files/debian/tee-supplicant.service
> index 4508a142..f79e1984 100644
> --- a/meta/recipes-bsp/optee-client/files/debian/tee-supplicant.service
> +++ b/meta/recipes-bsp/optee-client/files/debian/tee-supplicant.service
> @@ -14,7 +14,7 @@ RemainAfterExit=yes
> # Start if not already started by the initramfs hook
> ExecStart=/bin/sh -c '/usr/bin/pgrep tee-supplicant >/dev/null || /usr/sbin/tee-supplicant -d'
> ExecStop=/bin/sh -c '/usr/bin/findmnt /sys/firmware/efi/efivars >/dev/null && /usr/bin/umount /sys/firmware/efi/efivars || true'
> -ExecStop=/bin/sh -c '/usr/sbin/modinfo -n tpm_ftpm_tee | /usr/bin/grep -E "\.ko$" >/dev/null && /usr/sbin/modprobe -r tpm_ftpm_tee || true'
> +ExecStop=/bin/sh -c '/usr/sbin/modinfo -n tpm_ftpm_tee | /usr/bin/grep -E "\\.ko$" >/dev/null && /usr/sbin/modprobe -r tpm_ftpm_tee || true'
> ExecStop=/usr/bin/pkill tee-supplicant
>
> [Install]
I probably have an even better solution than this, and I will re-post
all my OP-TEE fixes and cleanups as one series now. This became too messy.
Jan
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2023-07-20 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 11:24 Jan Kiszka
2023-07-20 16:25 ` Jan Kiszka [this message]
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=8f6cd1f7-b263-94ee-d909-4c61ecb3a5e4@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=baocheng.su@siemens.com \
--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