Github messages for voidlinux
 help / color / mirror / Atom feed
From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: dkms: update to 3.0.3
Date: Sun, 15 May 2022 22:16:43 +0200	[thread overview]
Message-ID: <20220515201643.Sx4NAZyP3dKuyog7WFW3zWGWweIOpEUnTJXoqOOJAp4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35026@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]

There's a closed pull request on the void-packages repository

dkms: update to 3.0.3
https://github.com/void-linux/void-packages/pull/35026

Description:
dkms: update to 3.0.3.

Main differences from 2.8.4:

- The following variables have been deprecated[^1]: REMAKE_INITRD, MODULES_CONF,
MODULES_CONF_OBSOLETES, MODULES_CONF_ALIAS_TYPE, MODULES_CONF_OBSOLETE_ONLY
- Print 'module/version' and not 'module, version' when doing `dkms status`[^2][^3].

Comparing the output of dkms-2.8.4 with dkms-3.0.3:

```console
$ dkms --version && dkms status
dkms-2.8.4
v4l2loopback, 0.12.5, 5.15.16_1, x86_64: installed
```

```console
$ dkms --version && dkms status
dkms-3.0.3
v4l2loopback/0.12.5, 5.15.16_1, x86_64: installed
```

[^1]: https://github.com/dell/dkms/commit/961f9ce
[^2]: https://github.com/dell/dkms/commit/f83b758
[^3]: https://github.com/dell/dkms/commit/65f01a0


<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-musl)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - ppc64le-musl


      parent reply	other threads:[~2022-05-15 20:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  7:01 [PR PATCH] " unspecd
2022-01-13  7:05 ` [PR PATCH] [Updated] " unspecd
2022-01-13  7:10 ` unspecd
2022-01-16 21:02 ` unspecd
2022-01-17  8:48 ` [PR REVIEW] " ericonr
2022-01-17  8:49 ` ericonr
2022-01-17  8:59 ` unspecd
2022-01-18 11:13 ` [PR PATCH] [Updated] " unspecd
2022-01-18 11:51 ` [PR REVIEW] " unspecd
2022-01-18 19:13 ` ericonr
2022-01-22  7:54 ` [PR PATCH] [Updated] " unspecd
2022-01-22  7:55 ` unspecd
2022-05-05 23:08 ` unspecd
2022-05-15 20:16 ` unspecd
2022-05-15 20:16 ` unspecd [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=20220515201643.Sx4NAZyP3dKuyog7WFW3zWGWweIOpEUnTJXoqOOJAp4@z \
    --to=unspecd@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).