From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: linux-firmware-dvb: remove conflicts with official linux-firmware
Date: Wed, 23 Nov 2022 07:31:33 +0100 [thread overview]
Message-ID: <20221123063133.5r6BunmuoTjOGyKkbqQ48dRqln1hC1QbKiDga50rBJ8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38683@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
There's a merged pull request on the void-packages repository
linux-firmware-dvb: remove conflicts with official linux-firmware
https://github.com/void-linux/void-packages/pull/38683
Description:
#### Testing the changes
- I tested the changes in this PR: **No**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl (crossbuild)
- armv7l (crossbuild)
- armv6l-musl (crossbuild)
#### Explanation
While trying to get the new linux-firmware #37081 working, conflicts are found with this
package. This is because some firmware is now also available in the official linux-firmware.
Since linux-firmware-dvb is still on version 20170329 and it seems there is no version that
is more recent than the official linux-firmware. I've removed all firmware that conflicts with
the linux-firmware-20220815 version.
prev parent reply other threads:[~2022-11-23 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 10:17 [PR PATCH] " dataCobra
2022-08-16 18:41 ` [PR PATCH] [Updated] " dataCobra
2022-08-17 4:55 ` dataCobra
2022-09-14 4:51 ` dataCobra
2022-10-06 19:31 ` dataCobra
2022-10-13 6:09 ` [PR PATCH] [Updated] " dataCobra
2022-10-14 8:02 ` dataCobra
2022-11-23 6:31 ` the-maldridge [this message]
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=20221123063133.5r6BunmuoTjOGyKkbqQ48dRqln1hC1QbKiDga50rBJ8@z \
--to=the-maldridge@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).