From: noarchwastaken <noarchwastaken@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [RFC] linux-firmware: pull from commit hash instead of tag
Date: Tue, 25 May 2021 04:11:25 +0200 [thread overview]
Message-ID: <20210525021125.OnWIhCOxgEHs7WeNVu8GBsaNB2tSEv3G2LzsmZBY3Q0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31105@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]
There is an updated pull request by noarchwastaken against master on the void-packages repository
https://github.com/noarchwastaken/void-packages linux-firmware-20210518
https://github.com/void-linux/void-packages/pull/31105
[RFC] linux-firmware: pull from commit hash instead of tag
This would enable faster support for new hardware, and avoid waiting for (possibly) two months just for `linux-firmware` to tag.
One can ask for hardware support with firmware not tagged yet but present in master, and we can update the commit hash to pull in that new firmware.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/31105.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-linux-firmware-20210518-31105.patch --]
[-- Type: text/x-diff, Size: 1430 bytes --]
From 497e5214bf05ffd70eb45c646ed75dce207148f2 Mon Sep 17 00:00:00 2001
From: noarchwastaken <noarch@n0ar.ch>
Date: Mon, 24 May 2021 21:51:53 -0400
Subject: [PATCH] linux-firmware: update to 20210518.
---
srcpkgs/linux-firmware/template | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/linux-firmware/template b/srcpkgs/linux-firmware/template
index 66358c052182..3e6728b8d572 100644
--- a/srcpkgs/linux-firmware/template
+++ b/srcpkgs/linux-firmware/template
@@ -1,14 +1,17 @@
# Template file for 'linux-firmware'
pkgname=linux-firmware
-version=20210511
+version=20210518
revision=1
+_commit=f8462923ed8fc874f770b8c6dfad49d39b381f14
+wrksrc="${pkgname}-${_commit}"
depends="${pkgname}-amd>=${version}_${revision} ${pkgname}-network>=${version}_${revision}"
short_desc="Binary firmware blobs for the Linux kernel"
maintainer="Érico Nogueira <ericonr@disroot.org>"
license="See /usr/share/licenses/${pkgname}"
homepage="https://www.kernel.org/"
-distfiles="https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/${pkgname}-${version}.tar.gz"
-checksum=4c38e6a15775e2911e60898804f1d5720f8e3992a79487a5c1b2250df49a11c4
+distfiles="https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/${pkgname}-${_commit}.tar.gz"
+
+checksum=d88e207528b49e7ddc75cd370f8b7733f0e62ef586bb0d8b8778264fd60837a0
python_version=3
nostrip=yes
next prev parent reply other threads:[~2021-05-25 2:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 2:07 [PR PATCH] " noarchwastaken
2021-05-25 2:09 ` [PR PATCH] [Updated] " noarchwastaken
2021-05-25 2:11 ` noarchwastaken [this message]
2021-05-25 3:36 ` abenson
2021-05-25 3:36 ` [PR REVIEW] " abenson
2021-05-25 3:42 ` [PR PATCH] [Updated] " noarchwastaken
2021-05-25 3:48 ` ericonr
2021-05-25 5:46 ` CameronNemo
2021-05-25 8:37 ` fosslinux
2021-05-25 13:21 ` noarchwastaken
2021-05-25 13:35 ` noarchwastaken
2022-04-15 16:09 ` tibequadorian
2022-04-15 16:50 ` [PR PATCH] [Closed]: " paper42
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=20210525021125.OnWIhCOxgEHs7WeNVu8GBsaNB2tSEv3G2LzsmZBY3Q0@z \
--to=noarchwastaken@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).