[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a88c47e98139a6264670879407fb09a3@redadmin.org>
Date: Wed, 17 Sep 2025 08:39:29 +0900
From: weibu@...admin.org
To: Jonathan Corbet <corbet@....net>
Cc: kvm@...r.kernel.org, pbonzini@...hat.com, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: wmi: lenovo-wmi-gamezone: fix typo in frequency
Hi Jon,
You’re right — that block is a verbatim MOF listing decoded by bmfdec,
and the misspelling comes from the vendor-provided Description string.
So this isn’t an editing error in the docs.
I’ll drop this patch. If it helps future readers, I can send a follow-up
that adds a short note saying the MOF listing is verbatim and typos are
preserved.
Thanks for the careful review!
Akiyoshi
2025-09-17 00:59 に Jonathan Corbet さんは書きました:
> Akiyoshi Kurita <weibu@...admin.org> writes:
>
>> Fix a spelling mistake in lenovo-wmi-gamezone.rst
>> ("freqency" -> "frequency").
>>
>> No functional change.
>>
>> Signed-off-by: Akiyoshi Kurita <weibu@...admin.org>
>> ---
>> Documentation/wmi/devices/lenovo-wmi-gamezone.rst | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/wmi/devices/lenovo-wmi-gamezone.rst
>> b/Documentation/wmi/devices/lenovo-wmi-gamezone.rst
>> index 997263e51a7d..167548929ac2 100644
>> --- a/Documentation/wmi/devices/lenovo-wmi-gamezone.rst
>> +++ b/Documentation/wmi/devices/lenovo-wmi-gamezone.rst
>> @@ -153,7 +153,7 @@ data using the `bmfdec
>> <https://github.com/pali/bmfdec>`_ utility:
>> [WmiDataId(1), read, Description("P-State ID.")] uint32 PStateID;
>> [WmiDataId(2), read, Description("CLOCK ID.")] uint32 ClockID;
>> [WmiDataId(3), read, Description("Default value.")] uint32
>> defaultvalue;
>> - [WmiDataId(4), read, Description("OC Offset freqency.")] uint32
>> OCOffsetFreq;
>> + [WmiDataId(4), read, Description("OC Offset frequency")] uint32
>> OCOffsetFreq;
>> [WmiDataId(5), read, Description("OC Min offset value.")] uint32
>> OCMinOffset;
>
> I don't have the device in question and can't test this ... but the
> text
> in question has the appearance of being literal output from the bmfdec
> utility. Do we know that this is some sort of editing error rather
> than
> an accurate reflection of what the tool prints?
>
> Thanks,
>
> jon
Powered by blists - more mailing lists