From: Navon John Lukose <navonjohnlukose@gmail.com>
To: "Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Sebastian Reichel <sre@kernel.org>,
platform-driver-x86@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] platform/x86: hp-wmi: Add charge behaviour support
Date: Wed, 27 May 2026 11:45:01 +0530 [thread overview]
Message-ID: <20260527061501.10943-1-navonjohnlukose@gmail.com> (raw)
In-Reply-To: <20260505200222.157144-1-navonjohnlukose@gmail.com>
Hi,
Gentle ping on this RFC.
Is this approach acceptable for hp-wmi, or would you prefer this to live
elsewhere / use different gating before I prepare a non-RFC version?
Thanks,
Navon
next parent reply other threads:[~2026-05-27 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260505200222.157144-1-navonjohnlukose@gmail.com>
2026-05-27 6:15 ` Navon John Lukose [this message]
2026-05-31 18:13 ` [RFC PATCH v2] platform/x86: hp-wmi: Add charge behaviour support Navon John Lukose
2026-07-07 13:06 ` Ilpo Järvinen
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=20260527061501.10943-1-navonjohnlukose@gmail.com \
--to=navonjohnlukose@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sre@kernel.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