Github messages for voidlinux
 help / color / mirror / Atom feed
From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux-firmware: update to 20220708
Date: Tue, 23 Aug 2022 13:30:53 +0200	[thread overview]
Message-ID: <20220823113053.7r8bk1qsCL4AcfrQn1MvTnfCFnQHU-00oDY7Q4V0GGA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37081@inbox.vuxu.org>

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

New comment by dataCobra on void-packages repository

https://github.com/void-linux/void-packages/pull/37081#issuecomment-1223934681

Comment:
I've successful tested this PR on 3 different systems.


@ericonr I've created a PR https://github.com/void-linux/void-packages/pull/38683 to get rid of the conflicts between the two packages. Since linux-firmware-dvb has firmware remaining that is not yet in linux-firmware.
-> (linux-firmware-dvb: remove conflicts with official linux-firmware)

  parent reply	other threads:[~2022-08-23 11:30 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 11:47 [PR PATCH] linux-firmware: update to 20220509 absrd
2022-05-14  0:30 ` ericonr
2022-08-12  2:14 ` github-actions
2022-08-15 15:04 ` [PR PATCH] [Updated] " absrd
2022-08-15 15:05 ` absrd
2022-08-23 11:26 ` linux-firmware: update to 20220708 dataCobra
2022-08-23 11:28 ` dataCobra
2022-08-23 11:29 ` dataCobra
2022-08-23 11:30 ` dataCobra [this message]
2022-08-24  5:58 ` dataCobra
2022-08-24 12:55 ` [PR PATCH] [Updated] " absrd
2022-08-24 12:56 ` linux-firmware: update to 20220815 absrd
2022-08-24 12:57 ` dataCobra
2022-08-30  7:40 ` dataCobra
2022-09-14  4:30 ` dataCobra
2022-09-15 13:11 ` [PR PATCH] [Updated] " absrd
2022-09-15 13:11 ` linux-firmware: update to 20220913 absrd
2022-09-28 13:03 ` dataCobra
2022-09-28 13:03 ` dataCobra
2022-10-13  6:08 ` dataCobra
2022-10-13 12:02 ` [PR PATCH] [Updated] " absrd
2022-10-13 12:02 ` linux-firmware: update to 20221012 absrd
2022-11-09 14:56 ` vitezfh
2022-11-13 21:19 ` [PR PATCH] [Updated] " absrd
2022-11-13 21:20 ` linux-firmware: update to 20221109 absrd
2022-11-16 13:54 ` dataCobra
2022-11-16 23:44 ` [PR PATCH] [Updated] " absrd
2022-11-23  6:35 ` the-maldridge
2022-11-23  6:38 ` classabbyamp
2022-11-23 15:56 ` [PR PATCH] [Updated] " absrd
2022-11-23 20:31 ` JamiKettunen
2022-11-23 23:50 ` classabbyamp
2022-11-23 23:51 ` classabbyamp
2022-11-24  8:58 ` dataCobra
2022-11-24  8:58 ` dataCobra
2022-11-24  9:02 ` classabbyamp
2022-11-24  9:11 ` dataCobra
2022-11-24  9:18 ` classabbyamp
2022-11-24  9:21 ` dataCobra
2022-11-24  9:22 ` dataCobra
2022-11-24 13:34 ` [PR PATCH] [Updated] " absrd
2022-11-25  5:38 ` dataCobra
2022-11-25  5:40 ` [PR PATCH] [Merged]: " classabbyamp
2022-06-12 12:49 [PR PATCH] linux-firmware: update to 20220610 steinex
2022-08-16  5:46 ` linux-firmware: update to 20220708 biopsin
2022-10-13  6:03 ` dataCobra
2022-07-17  6:37 [PR PATCH] " MouadCharradi
2022-08-11 18:22 ` dataCobra
2022-08-11 18:23 ` dataCobra
2022-08-11 18:35 ` dataCobra
2022-08-11 20:19 ` MouadCharradi
2022-08-11 21:12 ` paper42
2022-08-15 10:20 ` dataCobra
2022-08-15 11:11 ` MouadCharradi
2022-08-16  5:47 ` biopsin
2022-08-23 11:27 ` dataCobra
2022-08-26 18:52 ` MouadCharradi

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=20220823113053.7r8bk1qsCL4AcfrQn1MvTnfCFnQHU-00oDY7Q4V0GGA@z \
    --to=datacobra@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).