Github messages for voidlinux
 help / color / mirror / Atom feed
From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: warnings and errors in dmesg with 5.13 series kernel
Date: Thu, 15 Jul 2021 09:29:33 +0200	[thread overview]
Message-ID: <20210715072933.eLll1_qQ7AubBc20ygxR-MEDiKmtyo8JJfs3O0VoY_s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31968@inbox.vuxu.org>

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

New comment by dkwo on void-packages repository

https://github.com/void-linux/void-packages/issues/31968#issuecomment-880464690

Comment:
Thanks for pointing that out.

I've been trying forever to get rid of `acpi_call`.
The required patch (to make certain `tlp` battery discharge functions work on thinkpads) has been tested and even approved by Lenovo, but the subsystem maintainer refuses to merge it, on the ground that they want to avoid defining new power_supply class userspace API inside drivers/platform/x86 https://patchwork.kernel.org/project/platform-driver-x86/patch/c2504700-06e9-e7d8-80f7-de90b0b6dfb5@gmail.com/

Would it make sense to patch Void kernel?

If that's not possible, should I patch `acpi_call` instead (which also has not been updated for ages)?

  parent reply	other threads:[~2021-07-15  7:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 19:30 [ISSUE] " dkwo
2021-07-14 19:42 ` ericonr
2021-07-14 19:45 ` leahneukirchen
2021-07-14 20:12 ` leahneukirchen
2021-07-15  7:29 ` dkwo [this message]
2021-07-15 10:03 ` leahneukirchen
2021-07-17 15:06 ` dkwo
2021-07-21  7:38 ` [ISSUE] [CLOSED] " dkwo

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=20210715072933.eLll1_qQ7AubBc20ygxR-MEDiKmtyo8JJfs3O0VoY_s@z \
    --to=dkwo@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).