From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Denis Benato <denis.benato@linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
Hans de Goede <hansg@kernel.org>,
"Limonciello, Mario" <mario.limonciello@amd.com>,
"Luke D . Jones" <luke@ljones.dev>,
Alok Tiwari <alok.a.tiwari@oracle.com>,
Derek John Clark <derekjohn.clark@gmail.com>,
Mateusz Schyboll <dragonn@op.pl>,
porfet828@gmail.com, Denis Benato <benato.denis96@gmail.com>
Subject: Re: [PATCH] platform/x86: asus-armoury: fix wording of a comment
Date: Tue, 18 Nov 2025 11:19:59 +0200 (EET) [thread overview]
Message-ID: <7ceec028-34ce-df22-173b-017c0a1f8424@linux.intel.com> (raw)
In-Reply-To: <20251115145649.1174238-1-denis.benato@linux.dev>
On Sat, 15 Nov 2025, Denis Benato wrote:
> Drop the repeated word "known" from the comment
> "No known problems are known for this dev_id".
>
> Signed-off-by: Denis Benato <denis.benato@linux.dev>
> ---
> drivers/platform/x86/asus-armoury.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/asus-armoury.c b/drivers/platform/x86/asus-armoury.c
> index 31a3046b7d63..c3026e1d3ce2 100644
> --- a/drivers/platform/x86/asus-armoury.c
> +++ b/drivers/platform/x86/asus-armoury.c
> @@ -242,7 +242,7 @@ static int armoury_set_devstate(struct kobj_attribute *attr,
> pr_err("Refusing to write to readonly devstate part of unsafe interface\n");
> return -EINVAL;
> default:
> - /* No known problems are known for this dev_id */
> + /* No problems are known for this dev_id */
> break;
> }
Thanks. While taking the cores change out, I also folded this in to the
original change.
--
i.
prev parent reply other threads:[~2025-11-18 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 14:56 [PATCH] platform/x86: asus-armoury: fix wording of a comment Denis Benato
2025-11-18 9:19 ` 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=7ceec028-34ce-df22-173b-017c0a1f8424@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=benato.denis96@gmail.com \
--cc=denis.benato@linux.dev \
--cc=derekjohn.clark@gmail.com \
--cc=dragonn@op.pl \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=porfet828@gmail.com \
/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