From: Animeshz <Animeshz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] linux-firmware: update to 20211027
Date: Sat, 30 Oct 2021 20:00:39 +0200 [thread overview]
Message-ID: <20211030180039.CTx-d9BX1a8A2D-1VzTx0oVcgdoWvIpDOlUS5xhlgzw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33786@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
There is an updated pull request by Animeshz against master on the void-packages repository
https://github.com/Animeshz/void-packages master
https://github.com/void-linux/void-packages/pull/33786
linux-firmware: update to 20211027
#### 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
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [ ] 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/33786.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-33786.patch --]
[-- Type: text/x-diff, Size: 1290 bytes --]
From 8d879f3c386808b5706b1127723d83caec87d66d Mon Sep 17 00:00:00 2001
From: Animesh Sahu <animeshsahu19@yahoo.com>
Date: Wed, 27 Oct 2021 19:39:14 +0530
Subject: [PATCH] linux-firmware: update to 20211027
---
srcpkgs/linux-firmware/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/linux-firmware/template b/srcpkgs/linux-firmware/template
index d5ecfbe866db..36e802ac7d82 100644
--- a/srcpkgs/linux-firmware/template
+++ b/srcpkgs/linux-firmware/template
@@ -1,6 +1,6 @@
# Template file for 'linux-firmware'
pkgname=linux-firmware
-version=20210818
+version=20211027
revision=1
depends="${pkgname}-amd>=${version}_${revision} ${pkgname}-network>=${version}_${revision}"
short_desc="Binary firmware blobs for the Linux kernel"
@@ -8,8 +8,8 @@ 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=ccf1b5ffece2eee801ae787e81010ab89786e4f0ffb4bd4f2209413901988220
python_version=3
+checksum=7667d054faed0cc07c3dfc858503987b21e7cfb4ba44368e3e138c8ea87859d9
nostrip=yes
subpackages="linux-firmware-amd linux-firmware-broadcom
next prev parent reply other threads:[~2021-10-30 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 14:11 [PR PATCH] linux-firmware: update to 20210919 Animeshz
2021-10-29 4:07 ` zdykstra
2021-10-29 4:21 ` Animeshz
2021-10-29 4:35 ` [PR PATCH] [Updated] " Animeshz
2021-10-30 17:56 ` linux-firmware: update to 20211027 ericonr
2021-10-30 18:00 ` Animeshz [this message]
2021-10-31 2:48 ` [PR PATCH] [Updated] " Animeshz
2021-10-31 2:49 ` Animeshz
2021-10-31 2:53 ` [PR PATCH] [Updated] " Animeshz
2021-11-04 17:30 ` [PR PATCH] [Merged]: " ericonr
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=20211030180039.CTx-d9BX1a8A2D-1VzTx0oVcgdoWvIpDOlUS5xhlgzw@z \
--to=animeshz@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).