From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: cross-built kernel/dkms improvements
Date: Sun, 01 Oct 2023 22:21:09 +0200 [thread overview]
Message-ID: <20231001202109.FZh5fZWGgRKDv91AN7zMdp5lLbWh2T-wDlN9yb0amFs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46332@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
There's a merged pull request on the void-packages repository
cross-built kernel/dkms improvements
https://github.com/void-linux/void-packages/pull/46332
Description:
- dkms: allow limiting jobs, add missing dep
- some less-powerful platforms may be overwhelmed by the default `-j$(nproc)`. Allow overriding this by setting `DKMS_JOBS` in `/etc/default/dkms`
- `bc` is needed for `make prepare0` on kernel 6.1+, which is run on cross.
- see also: https://github.com/void-linux/void-packages/pull/46152#issuecomment-1741479613
- linux6.1: include files necessary for dkms on cross
- linux6.5: include files necessary for dkms on cross
The same fix could be applied to linux6.3 and linux6.4, but with the impending zfs 2.1.13 bump (#46304), I don't see much point.
fixes #44807
#### Testing the changes
- I tested the changes in this PR: **YES** (tested in an aarch64-musl VM on 6.3 with several dkms modules)
@moabeat-berlin, @r-ricci, @Calandracas606: please test
[ci skip]
prev parent reply other threads:[~2023-10-01 20:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 21:59 [PR PATCH] " classabbyamp
2023-09-30 1:14 ` [PR PATCH] [Updated] " classabbyamp
2023-09-30 16:46 ` Calandracas606
2023-09-30 16:49 ` Calandracas606
2023-09-30 16:54 ` classabbyamp
2023-09-30 16:54 ` classabbyamp
2023-09-30 17:05 ` Calandracas606
2023-09-30 18:21 ` moabeat-berlin
2023-09-30 22:30 ` moabeat-berlin
2023-10-01 1:06 ` classabbyamp
2023-10-01 1:06 ` classabbyamp
2023-10-01 1:59 ` [PR PATCH] [Updated] " classabbyamp
2023-10-01 3:09 ` Calandracas606
2023-10-01 4:40 ` [PR PATCH] [Updated] " classabbyamp
2023-10-01 10:02 ` moabeat-berlin
2023-10-01 10:03 ` moabeat-berlin
2023-10-01 15:42 ` Calandracas606
2023-10-01 20:15 ` moabeat-berlin
2023-10-01 20:21 ` classabbyamp [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=20231001202109.FZh5fZWGgRKDv91AN7zMdp5lLbWh2T-wDlN9yb0amFs@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).