From: Proximyst <Proximyst@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] linux-firmware: move MediaTek firmware
Date: Fri, 24 Apr 2020 18:48:04 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21304@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
There is a new pull request by Proximyst against master on the void-packages repository
https://github.com/Proximyst/void-packages patch-1
https://github.com/void-linux/void-packages/pull/21304
linux-firmware: move MediaTek firmware
A patch file from https://github.com/void-linux/void-packages/pull/21304.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-21304.patch --]
[-- Type: text/x-diff, Size: 768 bytes --]
From 4fae5531fb0f043c80887c0e07f4f6fb16195b4c Mon Sep 17 00:00:00 2001
From: Mariell <proximyst@proximyst.com>
Date: Fri, 24 Apr 2020 18:47:55 +0200
Subject: [PATCH] linux-firmware: move MediaTek firmware
---
srcpkgs/linux-firmware/template | 1 +
1 file changed, 1 insertion(+)
diff --git a/srcpkgs/linux-firmware/template b/srcpkgs/linux-firmware/template
index dddc40ca911..20dff5efee6 100644
--- a/srcpkgs/linux-firmware/template
+++ b/srcpkgs/linux-firmware/template
@@ -69,6 +69,7 @@ linux-firmware-network_package() {
vmove usr/lib/firmware/kaweth
vmove usr/lib/firmware/libertas
vmove usr/lib/firmware/mrvl
+ vmove usr/lib/firmware/mt*
vmove usr/lib/firmware/ueagle-atm
vmove usr/lib/firmware/ti-connectivity
vmove usr/lib/firmware/dpaa2
next reply other threads:[~2020-04-24 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 16:48 Proximyst [this message]
2020-04-25 10:01 ` [PR PATCH] [Updated] " Proximyst
2020-04-25 10:02 ` Proximyst
2020-04-25 21:27 ` Proximyst
2020-04-26 12:31 ` [PR PATCH] [Merged]: " Hoshpak
2022-03-13 6:23 [PR PATCH] " Sapein
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-21304@inbox.vuxu.org \
--to=proximyst@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).