From: Jan Kiszka <jan.kiszka@siemens.com>
To: Adriaan Schmidt <adriaan.schmidt@siemens.com>,
isar-users@googlegroups.com
Cc: stefan-koch@siemens.com
Subject: Re: [PATCH 0/3] Kbuild follow-up
Date: Thu, 9 May 2024 19:35:04 +0200 [thread overview]
Message-ID: <e56ce361-2643-420e-b36b-150463da1344@siemens.com> (raw)
In-Reply-To: <20240509103409.2762062-1-adriaan.schmidt@siemens.com>
On 09.05.24 12:34, Adriaan Schmidt wrote:
> Based on the Stefan's "[PATCH] linux-module: Support emulated module build
> with cross-compiled kernel", and on the result of staring at dependency
> graphs with Jan, this mainly addresses corner cases of the refactored
> kbuild packaging when cross-compiling.
>
> I've tested
>
> - cross-compiled custom kernel and cross module build
> - cross-compiled custom kernel and emulated module build
> - distro kernel and emulated module build
>
> Let me know if one of your use-cases is still missing.
>
> Also including some fixups brought up in recent reviews on the ML.
>
> Adriaan
>
> Adriaan Schmidt (3):
> module.inc: fix kbuild dependency
> linux-custom: use to_boolean when checking ISAR_CROSS_COMPILE
> kbuildtarget.bbclass: add missing license header
>
> meta/recipes-kernel/linux-module/module.inc | 5 ++++-
> meta/recipes-kernel/linux/classes/kbuildtarget.bbclass | 5 +++++
> meta/recipes-kernel/linux/linux-custom.inc | 5 +----
> meta/recipes-kernel/linux/linux-distro.bb | 1 +
> 4 files changed, 11 insertions(+), 5 deletions(-)
>
Thanks for the cleanups!
Jan
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2024-05-09 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 10:34 Adriaan Schmidt
2024-05-09 10:34 ` [PATCH 1/3] module.inc: fix kbuild dependency Adriaan Schmidt
2024-05-09 17:35 ` Jan Kiszka
2024-05-10 4:44 ` Schmidt, Adriaan
2024-05-09 10:34 ` [PATCH 2/3] linux-custom: use to_boolean when checking ISAR_CROSS_COMPILE Adriaan Schmidt
2024-05-09 10:34 ` [PATCH 3/3] kbuildtarget.bbclass: add missing license header Adriaan Schmidt
2024-05-09 17:35 ` 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=e56ce361-2643-420e-b36b-150463da1344@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=stefan-koch@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