Github messages for voidlinux
 help / color / mirror / Atom feed
From: Sapein <Sapein@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] linux-firmware: move MediaTek firmware
Date: Mon, 14 Mar 2022 22:36:54 +0100	[thread overview]
Message-ID: <20220314213654.VZq2x5eKjcK2b84ULWFkAp5jms7LV9sCbSP1w2CGoOw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36120@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 446 bytes --]

There is an updated pull request by Sapein against master on the void-packages repository

https://github.com/Sapein/void-packages master
https://github.com/void-linux/void-packages/pull/36120

linux-firmware: move MediaTek firmware
Currently only some MediaTek firmware is moved.

#### Testing the changes
- I tested the changes in this PR: **YES**


A patch file from https://github.com/void-linux/void-packages/pull/36120.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-36120.patch --]
[-- Type: text/x-diff, Size: 1181 bytes --]

From ef836ddb72c611f9c062f3da3d23db1c7c4e1033 Mon Sep 17 00:00:00 2001
From: Sapein <5852983+Sapein@users.noreply.github.com>
Date: Sun, 13 Mar 2022 00:05:24 +0000
Subject: [PATCH] linux-firmware: move MediaTek firmware

Currently only some MediaTek firmware is moved.
---
 srcpkgs/linux-firmware/template | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/linux-firmware/template b/srcpkgs/linux-firmware/template
index 7c55a94b343c..f782687ffcdb 100644
--- a/srcpkgs/linux-firmware/template
+++ b/srcpkgs/linux-firmware/template
@@ -1,7 +1,7 @@
 # Template file for 'linux-firmware'
 pkgname=linux-firmware
 version=20220209
-revision=1
+revision=2
 depends="${pkgname}-amd>=${version}_${revision} ${pkgname}-network>=${version}_${revision}"
 short_desc="Binary firmware blobs for the Linux kernel"
 maintainer="Érico Nogueira <ericonr@disroot.org>"
@@ -94,6 +94,7 @@ linux-firmware-network_package() {
 		vmove usr/lib/firmware/libertas
 		vmove usr/lib/firmware/mrvl
 		vmove "usr/lib/firmware/mt*.bin"
+		vmove usr/lib/firmware/mediatek
 		vmove usr/lib/firmware/ueagle-atm
 		vmove usr/lib/firmware/ti-connectivity
 		vmove usr/lib/firmware/dpaa2

  parent reply	other threads:[~2022-03-14 21:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13  6:23 [PR PATCH] " Sapein
2022-03-14 17:07 ` leahneukirchen
2022-03-14 21:36 ` Sapein [this message]
2022-03-14 21:38 ` [PR PATCH] [Updated] " Sapein
2022-03-15 13:49 ` leahneukirchen
2022-03-17 15:46 ` [PR REVIEW] " sgn
2022-03-17 16:26 ` Sapein
2022-03-21 21:01 ` [PR PATCH] [Updated] " Sapein
2022-03-22 21:47 ` Sapein
2022-03-22 21:53 ` Sapein
2022-03-23 13:39 ` paper42
2022-03-23 16:02 ` [PR PATCH] [Updated] " Sapein
2022-03-23 16:04 ` Sapein
2022-03-23 16:04 ` Sapein
2022-03-23 16:07 ` Sapein
2022-03-23 16:25 ` Sapein
2022-04-03 18:19 ` [PR PATCH] [Updated] " Sapein
2022-04-15  6:32 ` Sapein
2022-04-25 13:34 ` Sapein
2022-05-25 16:28 ` Sapein
2022-06-05 22:13 ` Sapein
2022-06-09 16:52 ` Sapein
2022-06-30  7:51 ` Sapein
2022-09-22 20:35 ` nicegamer7
2022-10-19 11:39 ` JamiKettunen
2022-10-19 11:40 ` JamiKettunen
2022-10-20  1:44 ` q66
2022-10-20  2:08 ` nicegamer7
2022-11-23 13:44 ` JamiKettunen
2022-11-23 13:51 ` Sapein
2022-12-02 21:41 ` Sapein
2022-12-02 21:47 ` [PR PATCH] [Updated] " Sapein
2022-12-10  2:30 ` Sapein
2023-03-24  1:54 ` github-actions
2023-04-08  1:48 ` [PR PATCH] [Closed]: " github-actions
  -- strict thread matches above, loose matches on Subject: below --
2020-04-24 16:48 [PR PATCH] " Proximyst
2020-04-25 10:01 ` [PR PATCH] [Updated] " Proximyst
2020-04-25 10:02 ` Proximyst
2020-04-25 21:27 ` Proximyst

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=20220314213654.VZq2x5eKjcK2b84ULWFkAp5jms7LV9sCbSP1w2CGoOw@z \
    --to=sapein@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).