From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Armandas Kvietkus <armundunelis@gmail.com>
Cc: luke@ljones.dev, denis.benato@linux.dev,
Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
fxzxaxon@outlook.com,
Armandas Kvietkus <armandas.kvietkus@proton.me>
Subject: Re: [PATCH] platform/x86: asus-wmi: suppress -ENODEV warning in fan_curve_get_factory_default()
Date: Wed, 6 May 2026 14:13:50 +0300 (EEST) [thread overview]
Message-ID: <777a250b-2913-8ec8-cef0-fc1b8f651692@linux.intel.com> (raw)
In-Reply-To: <20260503174752.26288-1-armundunelis@gmail.com>
On Sun, 3 May 2026, Armandas Kvietkus wrote:
> When the firmware does not support the fan curve WMI method,
> asus_wmi_evaluate_method_buf() returns -ENODEV. The caller
> fan_curve_check_present() already handles this gracefully by
> treating it as a non-error, but fan_curve_get_factory_default()
> still emits a pr_warn() before returning, producing spurious
> boot noise on unsupported hardware.
>
> Suppress the warning for -ENODEV only, consistent with how
> this error is handled elsewhere in asus-wmi.c.
>
> Reported-by: fxzxaxon@outlook.com
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221441
> Signed-off-by: Armandas Kvietkus <armandas.kvietkus@proton.me>
> ---
> drivers/platform/x86/asus-wmi.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/asus-wmi.c b/drivers/platform/x86/asus-wmi.c
> index 80144c412..9b12a9e1e 100644
> --- a/drivers/platform/x86/asus-wmi.c
> +++ b/drivers/platform/x86/asus-wmi.c
> @@ -3538,7 +3538,8 @@ static int fan_curve_get_factory_default(struct asus_wmi *asus, u32 fan_dev)
> err = asus_wmi_evaluate_method_buf(asus->dsts_id, fan_dev, mode, buf,
> FAN_CURVE_BUF_LEN);
> if (err) {
> - pr_warn("%s (0x%08x) failed: %d\n", __func__, fan_dev, err);
> + if (err != -ENODEV)
> + pr_warn("%s (0x%08x) failed: %d\n", __func__, fan_dev, err);
Hi,
If this print is useful at all, it looks more like it wants to be on debug
level which would also prevent the warning appearing in the logs unless
asked to.
Whenever something prints just __func__ and error codes, the line is
hardly meant for normal user consumption.
If you want to preserve this on warn level, the message has to be changed
as well to say the warning in plain English (preferrable in another
another patch).
(I prefer making it debug level.)
--
i.
prev parent reply other threads:[~2026-05-06 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 17:47 Armandas Kvietkus
2026-05-06 11:13 ` Ilpo Järvinen [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=777a250b-2913-8ec8-cef0-fc1b8f651692@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=armandas.kvietkus@proton.me \
--cc=armundunelis@gmail.com \
--cc=denis.benato@linux.dev \
--cc=fxzxaxon@outlook.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@vger.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
all inboxes | Powered by JetHome®