From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: linux-firmware: update to 20230210
Date: Thu, 09 Mar 2023 09:33:45 +0100 [thread overview]
Message-ID: <20230309083345.XR-kQM-e-Yyy0zR7DStjfkmNQ3TZ0u1B8l6ZGJHCnlo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41131@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
There's a merged pull request on the void-packages repository
linux-firmware: update to 20230210
https://github.com/void-linux/void-packages/pull/41131
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
prev parent reply other threads:[~2023-03-09 8:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 11:15 [PR PATCH] linux-firmware: update to 20221214 absrd
2022-12-16 15:06 ` [PR REVIEW] " paper42
2022-12-16 15:14 ` absrd
2022-12-17 13:59 ` icp1994
2022-12-17 19:38 ` brxken128
2023-01-18 1:11 ` [PR PATCH] [Updated] " absrd
2023-03-02 7:19 ` linux-firmware: update to 20230117 dataCobra
2023-03-02 7:19 ` dataCobra
2023-03-02 21:05 ` [PR PATCH] [Updated] " absrd
2023-03-09 7:19 ` linux-firmware: update to 20230210 omnisci3nce
2023-03-09 8:04 ` brxken128
2023-03-09 8:33 ` sgn [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=20230309083345.XR-kQM-e-Yyy0zR7DStjfkmNQ3TZ0u1B8l6ZGJHCnlo@z \
--to=sgn@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).