From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Moessbauer,
Felix (T RDA IOT SES-DE)" <felix.moessbauer@siemens.com>,
"Schild, Henning (T RDA IOT SES-DE)" <henning.schild@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/1] Add support to build binary version of DKMS kernel modules
Date: Mon, 19 Apr 2021 15:33:58 +0200 [thread overview]
Message-ID: <9ea0c0fa-56fc-a16d-d5ab-7b5d7849ad7e@siemens.com> (raw)
In-Reply-To: <AM0PR10MB1939C871606D5D0302D1A9AB89499@AM0PR10MB1939.EURPRD10.PROD.OUTLOOK.COM>
On 19.04.21 14:45, Moessbauer, Felix (T RDA IOT SES-DE) wrote:
> Hi,
>
> I just added it to the CI and did some early tests with the v4l2loopback module.
> For x86 and arm64, things run smooth, but for armv7 the module cannot be build (even after disabling crossbuilds).
>
> This seems to be not an ISAR issue, but an upstream bug in the module DKMS itself.
>
> I'll have a closer look at that and push a v2 soon.
If it is an upstream bug, excluding that arch for now (with reference to
the Debian bug) would be fine.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-04-19 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 8:36 [PATCH 0/1] Add support to build binary version of DKMS kernel Felix Moessbauer
2021-04-14 8:36 ` [PATCH 1/1] Add support to build binary version of DKMS kernel modules Felix Moessbauer
2021-04-14 8:52 ` Henning Schild
2021-04-14 9:03 ` Jan Kiszka
2021-04-15 12:26 ` Henning Schild
2021-04-15 12:41 ` Raphael Lisicki
2021-04-15 12:52 ` Jan Kiszka
2021-04-19 12:45 ` Moessbauer, Felix
2021-04-19 13:33 ` Jan Kiszka [this message]
2021-04-22 10:44 ` Anton Mikanovich
2021-04-22 16:02 ` [PATCH v2 0/1] " Felix Moessbauer
2021-04-23 6:03 ` Jan Kiszka
2021-04-22 16:02 ` [PATCH v2 1/1] " Felix Moessbauer
2021-04-26 16:16 ` [PATCH v3 0/1] " Felix Moessbauer
2021-04-26 16:16 ` [PATCH v3 1/1] " Felix Moessbauer
2021-04-28 11:03 ` Anton Mikanovich
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=9ea0c0fa-56fc-a16d-d5ab-7b5d7849ad7e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@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