From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] tuxedo-drivers: update to 4.6.3
Date: Sun, 08 Sep 2024 10:03:17 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52143@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
There is a new pull request by newbluemoon against master on the void-packages repository
https://github.com/newbluemoon/void-packages tuxedo-drivers
https://github.com/void-linux/void-packages/pull/52143
tuxedo-drivers: update to 4.6.3
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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)
Built for kernels 5.15, 5.16, 5.18, 5.19, 6.0–6.10; running on 6.10.8.
A patch file from https://github.com/void-linux/void-packages/pull/52143.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tuxedo-drivers-52143.patch --]
[-- Type: text/x-diff, Size: 1999 bytes --]
From 194f10a08050e878270c055bc5e4b755cc34e701 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Sun, 8 Sep 2024 09:59:57 +0200
Subject: [PATCH] tuxedo-drivers: update to 4.6.3
---
srcpkgs/tuxedo-drivers/patches/kernel6.10.patch | 12 ------------
srcpkgs/tuxedo-drivers/template | 6 +++---
2 files changed, 3 insertions(+), 15 deletions(-)
delete mode 100644 srcpkgs/tuxedo-drivers/patches/kernel6.10.patch
diff --git a/srcpkgs/tuxedo-drivers/patches/kernel6.10.patch b/srcpkgs/tuxedo-drivers/patches/kernel6.10.patch
deleted file mode 100644
index e3441403ed2192..00000000000000
--- a/srcpkgs/tuxedo-drivers/patches/kernel6.10.patch
+++ /dev/null
@@ -1,12 +0,0 @@
---- a/src/clevo_acpi.c
-+++ b/src/clevo_acpi.c
-@@ -248,7 +248,9 @@ static const struct acpi_device_id clevo_acpi_device_ids[] = {
- static struct acpi_driver clevo_acpi_driver = {
- .name = DRIVER_NAME,
- .class = DRIVER_NAME,
-+#if LINUX_VERSION_CODE < KERNEL_VERSION(6, 10, 0)
- .owner = THIS_MODULE,
-+#endif
- .ids = clevo_acpi_device_ids,
- .flags = ACPI_DRIVER_ALL_NOTIFY_EVENTS,
- .ops = {
diff --git a/srcpkgs/tuxedo-drivers/template b/srcpkgs/tuxedo-drivers/template
index e9ecb3e8f793a7..7c4e576f70d2ad 100644
--- a/srcpkgs/tuxedo-drivers/template
+++ b/srcpkgs/tuxedo-drivers/template
@@ -1,14 +1,14 @@
# Template file for 'tuxedo-drivers'
pkgname=tuxedo-drivers
-version=4.6.1
-revision=2
+version=4.6.3
+revision=1
depends="dkms"
short_desc="TUXEDO hardware drivers"
maintainer="newbluemoon <blaumolch@mailbox.org>"
license="GPL-3.0-or-later"
homepage="https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers"
distfiles="https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/archive/v${version}/tuxedo-drivers-v${version}.tar.gz"
-checksum=be39bd3bff536c74e97bd66fff60c42f86c98f3c4d5b515ea94966b411427823
+checksum=d11e581c0d5e954fc856495cc9657519a6b69f830b7f88d34994ad5a186e09c5
dkms_modules="tuxedo-drivers ${version}"
next reply other threads:[~2024-09-08 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 8:03 newbluemoon [this message]
2024-09-15 13:26 ` [PR PATCH] [Updated] " newbluemoon
2024-09-18 2:12 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52143@inbox.vuxu.org \
--to=newbluemoon@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).