From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] tuxedo-drivers: update to 4.5.3
Date: Sat, 29 Jun 2024 09:15:09 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51040@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1193 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/51040
tuxedo-drivers: update to 4.5.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)
- builds on kernels 5.15, 5.16, 5.18, 5.19, 6.0 through 6.9, running on 6.9.6
A patch file from https://github.com/void-linux/void-packages/pull/51040.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tuxedo-drivers-51040.patch --]
[-- Type: text/x-diff, Size: 1181 bytes --]
From 61e0d9ed8cb799de99f88e2b482bf9e602a0dc57 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Sat, 29 Jun 2024 08:33:15 +0200
Subject: [PATCH] tuxedo-drivers: update to 4.5.3
---
srcpkgs/tuxedo-drivers/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/tuxedo-drivers/template b/srcpkgs/tuxedo-drivers/template
index f64d9ac2d43426..123b1eda4012f3 100644
--- a/srcpkgs/tuxedo-drivers/template
+++ b/srcpkgs/tuxedo-drivers/template
@@ -1,6 +1,6 @@
# Template file for 'tuxedo-drivers'
pkgname=tuxedo-drivers
-version=4.5.0
+version=4.5.3
revision=1
depends="dkms"
short_desc="TUXEDO hardware drivers"
@@ -8,7 +8,7 @@ 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=b68d38a0f6d57c80c5cd63fb2e235dcf1808d3e98253a096c91757d73dad5fa4
+checksum=73700f70eb6f90519d99e1fdc34f5ebdeeb6f079945d169f1dae8efaaf85cf97
dkms_modules="tuxedo-drivers ${version}"
next reply other threads:[~2024-06-29 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-29 7:15 newbluemoon [this message]
2024-07-01 15:28 ` [PR PATCH] [Merged]: " ahesford
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-51040@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).