From: zdykstra <zdykstra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] linux-fimrware: update to 20231111.
Date: Wed, 29 Nov 2023 03:34:55 +0100 [thread overview]
Message-ID: <20231129023455.pWQFu8Y-WB_Icr6neigO5H35OOybmQV6P9XTZbsOZII@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47477@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
There is an updated pull request by zdykstra against master on the void-packages repository
https://github.com/zdykstra/void-packages qualcrap
https://github.com/void-linux/void-packages/pull/47477
linux-fimrware: update to 20231111.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
The next tagged version of linux-firmware can do away with `rdfind` and `which` as makedepends - https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/copy-firmware.sh .
A patch file from https://github.com/void-linux/void-packages/pull/47477.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-qualcrap-47477.patch --]
[-- Type: text/x-diff, Size: 1310 bytes --]
From fe787ce93ac8c1750dbc0d2585ac7b8864f5e8f3 Mon Sep 17 00:00:00 2001
From: Zach Dykstra <dykstra.zachary@gmail.com>
Date: Tue, 28 Nov 2023 19:55:14 -0600
Subject: [PATCH] linux-fimrware: update to 20231111.
---
srcpkgs/linux-firmware/template | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/linux-firmware/template b/srcpkgs/linux-firmware/template
index 2cb3618ffd9eb..28a471e8233fa 100644
--- a/srcpkgs/linux-firmware/template
+++ b/srcpkgs/linux-firmware/template
@@ -1,14 +1,16 @@
# Template file for 'linux-firmware'
pkgname=linux-firmware
-version=20230804
+version=20231111
revision=1
+hostmakedepends="rdfind which"
+makedepends="rdfind which"
depends="linux-firmware-amd>=${version}_${revision} linux-firmware-network>=${version}_${revision}"
short_desc="Binary firmware blobs for the Linux kernel"
maintainer="Érico Nogueira <ericonr@disroot.org>"
license="custom:see /usr/share/licenses/linux-firmware"
homepage="https://www.kernel.org/"
distfiles="https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-${version}.tar.gz"
-checksum=c09913f675bea9623798eebf8b238cda49b62dfa1729cc7c2c17193b0ab22ff7
+checksum=80bfc46e3fc43820331a965354f5a3a9b478df90b07e2f39d9ddebc67ae0b23a
python_version=3
nostrip=yes
next prev parent reply other threads:[~2023-11-29 2:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 1:59 [PR PATCH] " zdykstra
2023-11-29 2:27 ` [PR PATCH] [Updated] " zdykstra
2023-11-29 2:34 ` zdykstra [this message]
2023-11-29 13:51 ` zdykstra
2023-11-29 22:10 ` [PR REVIEW] " classabbyamp
2023-11-29 22:47 ` [PR PATCH] [Updated] " zdykstra
2023-12-02 6:11 ` [PR PATCH] [Merged]: linux-firmware: " 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=20231129023455.pWQFu8Y-WB_Icr6neigO5H35OOybmQV6P9XTZbsOZII@z \
--to=zdykstra@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).