From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"pingfang.liao@outlook.com" <pingfang.liao@outlook.com>
Cc: "Liao, Pingfang (Marshell)" <Pingfang.Liao@siemens.com>
Subject: Re: [PATCH] fix: remove unsigned example module before including the signed one
Date: Thu, 25 May 2023 09:53:40 +0000 [thread overview]
Message-ID: <1043c10aebfe642bcd3a9a102c1823d7a9335095.camel@siemens.com> (raw)
In-Reply-To: <TYCP286MB16128E70087109D831DEEBCEE7469@TYCP286MB1612.JPNP286.PROD.OUTLOOK.COM>
On Thu, 2023-05-25 at 03:06 -0400, Pingfang Liao wrote:
> We need remove unsigned exmple module firstly, because signed and
> unsigned
> exmaple module will install example-module.ko to the same path, which
> will
> lead to dpkg error.
> ---
> meta-isar/conf/multiconfig/qemuamd64-sb-bullseye.conf | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta-isar/conf/multiconfig/qemuamd64-sb-bullseye.conf
> b/meta-isar/conf/multiconfig/qemuamd64-sb-bullseye.conf
> index 19a105e..ca76685 100644
> --- a/meta-isar/conf/multiconfig/qemuamd64-sb-bullseye.conf
> +++ b/meta-isar/conf/multiconfig/qemuamd64-sb-bullseye.conf
> @@ -4,7 +4,8 @@ DISTRO ?= "debian-bullseye"
>
> # include public keys
> IMAGE_INSTALL += "sb-mok-public"
> -# include signed example module
> +# remove unsigned example module and include signed example module
> +IMAGE_INSTALL:remove = "example-module-${KERNEL_NAME}"
Good catch, thanks.
ACK!
> IMAGE_INSTALL += "example-module-signed-${KERNEL_NAME}"
>
> # add MOK utilities to insert MOK into EFI
next prev parent reply other threads:[~2023-05-25 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 7:06 Pingfang Liao
2023-05-25 9:53 ` MOESSBAUER, Felix [this message]
2023-05-25 9:56 ` MOESSBAUER, Felix
2023-05-25 16:24 ` Jan Kiszka
2023-05-29 2:19 ` Liao, Pingfang (Marshell)
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=1043c10aebfe642bcd3a9a102c1823d7a9335095.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=Pingfang.Liao@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=pingfang.liao@outlook.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