public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Larson, Chris' via isar-users" <isar-users@googlegroups.com>
To: "cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>,
	"Bezdeka, Florian" <florian.bezdeka@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 2/2] linux-module: inherit per-kernel
Date: Tue, 8 Apr 2025 17:12:37 +0000	[thread overview]
Message-ID: <c59de312-59a6-4c89-95c1-866550e06e5c@siemens.com> (raw)
In-Reply-To: <f2a3004fbdef07c642f800a9c8d1854223eb1d80.camel@siemens.com>

On 4/8/2025 1:13 AM, Hombourger, Cedric (FT FDS CES LX) wrote:
> On Tue, 2025-04-08 at 10:07 +0200, Florian Bezdeka wrote:
>> On Mon, 2025-04-07 at 09:01 -0700, chris.larson via isar-users wrote:
>>> From: Christopher Larson <chris.larson@siemens.com>
>>>
>>> This ensures that it's possible to build the kernel module for all
>>> kernels which
>>> are supported by the current MACHINE. This will have no effect
>>> unless the
>>> KERNEL_NAMES variable is adjusted to add more than just
>>> KERNEL_NAME.
>>>
>>> Signed-off-by: Christopher Larson <chris.larson@siemens.com>
>>> ---
>>>   meta/recipes-kernel/linux-module/module.inc | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/meta/recipes-kernel/linux-module/module.inc
>>> b/meta/recipes-kernel/linux-module/module.inc
>>> index 3b0ceae7..47086158 100644
>>> --- a/meta/recipes-kernel/linux-module/module.inc
>>> +++ b/meta/recipes-kernel/linux-module/module.inc
>>> @@ -42,7 +42,7 @@ python() {
>>>           d.setVar('ISAR_CROSS_COMPILE', '0')
>>>   }
>>>   
>>> -inherit dpkg
>>> +inherit dpkg per-kernel
>>
>> AFAIR the rest of the code base uses one inherit statement per class.
> 
> Correct (just checked). On the other hand, meta-openembedded uses
> multiple the above construct very often (more often than not as far as
> I can tell).
> 
> I understand that isar and meta-openembedded are not the same projects
> but I would not nitpick on that as I don't think it hurts readability
> IMHO (it would if we had a dozen classes imported)

Apologies, I'm still adapting to the differences from Yocto. I have no objection to 
aligning this with isar repository convention in a v2. I did want to confirm that there was no objection to this feature before diving too deep into the tests, so I should have used an RFC prefix.
-- 
Christopher Larson
Siemens AG
www.siemens.com

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/c59de312-59a6-4c89-95c1-866550e06e5c%40siemens.com.

  reply	other threads:[~2025-04-08 17:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 16:01 [PATCH 0/2] Add support for per-kernel recipe variants chris.larson via isar-users
2025-04-07 16:01 ` [PATCH 1/2] per-kernel.bbclass: add class chris.larson via isar-users
2025-04-07 16:01 ` [PATCH 2/2] linux-module: inherit per-kernel chris.larson via isar-users
2025-04-07 19:25   ` 'cedric.hombourger@siemens.com' via isar-users
2025-04-08  8:07   ` 'Florian Bezdeka' via isar-users
2025-04-08  8:13     ` 'cedric.hombourger@siemens.com' via isar-users
2025-04-08 17:12       ` 'Larson, Chris' via isar-users [this message]
2025-04-08  8:09 ` [PATCH 0/2] Add support for per-kernel recipe variants 'Florian Bezdeka' via isar-users
2025-04-08  8:18   ` 'cedric.hombourger@siemens.com' via isar-users
2025-04-08  8:29     ` 'Florian Bezdeka' via isar-users
2025-04-08  8:34       ` 'cedric.hombourger@siemens.com' via isar-users
2025-04-08 10:05     ` 'Jan Kiszka' via isar-users
2025-04-08 10:29       ` 'cedric.hombourger@siemens.com' via isar-users

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=c59de312-59a6-4c89-95c1-866550e06e5c@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=chris.larson@siemens.com \
    --cc=florian.bezdeka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox