From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux-firmware: move MediaTek firmware
Date: Wed, 23 Nov 2022 14:44:11 +0100 [thread overview]
Message-ID: <20221123134411.FYsG-ZtPdGs-kEfxjLlxZsFzOZO_SGGJIewp9P3XDZE@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: 813 bytes --]
New comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/pull/36120#issuecomment-1325088040
Comment:
[Here's how Chimera Linux does it currently](https://github.com/chimera-linux/cports/blob/6d47cc1/main/firmware-linux/template.py#L82-L85), maybe we could do something similar? would allow us to separate the network-related and ARM SoC specific files by moving the ladder to a `linux-firmware-mediatek` subpackage and then bringing rest of `mediatek` dir and `mt7*.bin` into `linux-firmware-network`.
Also this commit currently is very vague: `linux-firmware: move MediaTek firmware`, move them *where*? obviously into `-network` subpackage but it could be more specific for commit history readability
@Sapein are you interested in continuing (to fix) this PR?
next prev parent reply other threads:[~2022-11-23 13:44 UTC|newest]
Thread overview: 35+ 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 ` [PR PATCH] [Updated] " Sapein
2022-03-14 21:38 ` 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 [this message]
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
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=20221123134411.FYsG-ZtPdGs-kEfxjLlxZsFzOZO_SGGJIewp9P3XDZE@z \
--to=jamikettunen@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).