Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: rtl8192eu-dkms-2022.12.29
Date: Sun, 04 Jun 2023 04:12:00 +0200	[thread overview]
Message-ID: <20230604021200.46rJ39NOdzD7npkcd7kCvtTSe3ZUoAWPKA8iNGF--E0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30121@inbox.vuxu.org>

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

There's a closed pull request on the void-packages repository

New package: rtl8192eu-dkms-2022.12.29
https://github.com/void-linux/void-packages/pull/30121

Description:
<!-- Mark items with [x] where applicable -->

#### Purpose of this package

This package is necessary for using some versions of TP-Link TL-WN823N (because in-kernel rtl8xxxx module does not work properly for those devices).

#### Quality requirement
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements)
  --> The source repository does not provide releases

#### Have the results of the proposed changes been tested?
- [X] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
  On a x86_64 (glibc) system, with TP-Link TL-WN823N v2/v3

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


      parent reply	other threads:[~2023-06-04  2:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 14:26 [PR PATCH] New package: rtl8192eu-dkms-20210111 Phicem
2022-04-16 12:58 ` [PR PATCH] [Updated] " Phicem
2022-04-16 13:01 ` Phicem
2022-07-16  2:13 ` New package: rtl8192eu-dkms-20220406 github-actions
2022-07-27 20:25 ` Phicem
2022-10-27  2:13 ` github-actions
2022-11-05 17:27 ` [PR PATCH] [Updated] " Phicem
2022-11-05 17:30 ` Phicem
2022-11-05 18:05 ` [PR REVIEW] New package: rtl8192eu-dkms-20221031 paper42
2022-11-05 18:05 ` paper42
2022-11-05 18:05 ` paper42
2022-11-05 18:05 ` paper42
2022-11-06 18:56 ` Phicem
2022-11-06 19:09 ` Phicem
2022-11-20  0:01 ` classabbyamp
2023-02-18  1:59 ` github-actions
2023-02-18 20:05 ` [PR PATCH] [Updated] " Phicem
2023-02-18 20:08 ` [PR REVIEW] " Phicem
2023-02-18 20:10 ` Phicem
2023-05-21  1:56 ` New package: rtl8192eu-dkms-2022.12.29 github-actions
2023-06-04  2:12 ` github-actions [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=20230604021200.46rJ39NOdzD7npkcd7kCvtTSe3ZUoAWPKA8iNGF--E0@z \
    --to=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).