From: Mek101 <Mek101@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lm_sensors should include a service
Date: Sun, 04 Apr 2021 09:34:12 +0200 [thread overview]
Message-ID: <20210404073412.cDv1mwul27b7_g-r0IqIn91KMZeuU9okSO5O_LyAKMg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27525@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
New comment by Mek101 on void-packages repository
https://github.com/void-linux/void-packages/issues/27525#issuecomment-812988851
Comment:
Unfortunately, I don't have any patch: since I only tested the file streategy and what needs to be done; the modules to load change from system to system and the file must be generated and placed in `/etc/modules-load.d/` by the script linked above.
Perhaps, could you add the tag "Help wanted" to this issue", hoping that someone who knows how to write perl stubles upon it?
next prev parent reply other threads:[~2021-04-04 7:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 9:53 [ISSUE] lm_sensors service missing Mek101
2021-01-02 0:29 ` ericonr
2021-01-02 0:30 ` ericonr
2021-01-02 0:31 ` ericonr
2021-02-22 11:37 ` lm_sensors should include a service Mek101
2021-02-22 15:58 ` ericonr
2021-02-22 16:48 ` Mek101
2021-02-22 16:53 ` ericonr
2021-02-22 17:13 ` Mek101
2021-04-03 16:23 ` Mek101
2021-04-03 16:55 ` Mek101
2021-04-03 19:36 ` ericonr
2021-04-04 7:34 ` Mek101 [this message]
2021-04-04 20:20 ` ericonr
2021-04-20 19:56 ` thegarlynch
2021-04-20 20:07 ` Mek101
2021-04-21 17:31 ` thegarlynch
2021-04-21 17:41 ` Mek101
2021-04-21 17:44 ` Mek101
2021-04-21 17:45 ` thegarlynch
2021-04-21 17:48 ` Mek101
2021-12-22 12:08 ` CatalinCsnMaster
2021-12-22 12:09 ` CatalinCsnMaster
2021-12-22 12:26 ` Mek101
2021-12-22 12:26 ` Mek101
2021-12-22 12:27 ` Mek101
2022-05-01 2:15 ` github-actions
2022-05-01 15:19 ` Mek101
2022-05-01 15:19 ` Mek101
2022-05-01 15:40 ` Mek101
2022-05-01 19:10 ` ericonr
2022-07-31 2:14 ` github-actions
2022-08-14 2:14 ` [ISSUE] [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=20210404073412.cDv1mwul27b7_g-r0IqIn91KMZeuU9okSO5O_LyAKMg@z \
--to=mek101@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).