public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Liao, Pingfang (Marshell)" <Pingfang.Liao@siemens.com>
To: "Kiszka, Jan" <jan.kiszka@siemens.com>,
	"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"pingfang.liao@outlook.com" <pingfang.liao@outlook.com>
Subject: RE: [PATCH] fix: remove unsigned example module before including the signed one
Date: Mon, 29 May 2023 02:19:14 +0000	[thread overview]
Message-ID: <4a24eacc75f1494286cba0e93b68b3a6@siemens.com> (raw)
In-Reply-To: <1ebd119f-9ce1-9de0-d06c-c4779bf98513@siemens.com>

Thanks for the comments, will update the patch.

-----Original Message-----
From: Kiszka, Jan (T CED) <jan.kiszka@siemens.com> 
Sent: Friday, May 26, 2023 12:24 AM
To: MOESSBAUER, Felix (T CED INW-CN) <felix.moessbauer@siemens.com>; isar-users@googlegroups.com; pingfang.liao@outlook.com
Cc: Liao, Pingfang (Marshell) (DI FA CTR SVC&AI CN) <Pingfang.Liao@siemens.com>
Subject: Re: [PATCH] fix: remove unsigned example module before including the signed one

On 25.05.23 11:56, 'MOESSBAUER, Felix' via isar-users wrote:
> 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.
> 
> Please add the signed-off line to the commit message (git commit 
> --signoff). For details, see 
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki
> .linuxfoundation.org%2Fdco&data=05%7C01%7CPingfang.Liao%40ad011.siemen
> s.com%7C4cc19e2489704d47add908db5d3c78b1%7C38ae3bcd95794fd4addab42e149
> 5d55a%7C1%7C0%7C638206286528707710%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4
> wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7
> C&sdata=QNlWSFHmjvtEnaQAkRdUn8wF9DH6%2BDgHXqFyNwNg9T4%3D&reserved=0
> 

And fix the "exm[a]ple" typos at this chance. ;)

Thanks,
Jan

> Felix
> 
>> ---
>>  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}"
>>  IMAGE_INSTALL += "example-module-signed-${KERNEL_NAME}"
>>  
>>  # add MOK utilities to insert MOK into EFI
> 

--
Siemens AG, Technology
Competence Center Embedded Linux


      reply	other threads:[~2023-05-29  5:32 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
2023-05-25  9:56 ` MOESSBAUER, Felix
2023-05-25 16:24   ` Jan Kiszka
2023-05-29  2:19     ` Liao, Pingfang (Marshell) [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=4a24eacc75f1494286cba0e93b68b3a6@siemens.com \
    --to=pingfang.liao@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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