From: Hans de Goede <hdegoede@redhat.com>
To: Armin Wolf <W_Armin@gmx.de>, jithu.joseph@intel.com
Cc: ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: intel-wmi-sbl-fw-update: Fix function name in error message
Date: Mon, 15 Jan 2024 13:41:10 +0100 [thread overview]
Message-ID: <fe0d8cc6-8217-4fa6-bf37-6ce76ae51192@redhat.com> (raw)
In-Reply-To: <20240106224126.13803-1-W_Armin@gmx.de>
Hi,
On 1/6/24 23:41, Armin Wolf wrote:
> Since when the driver was converted to use the bus-based WMI
> interface, the old GUID-based WMI functions are not used anymore.
> Update the error message to avoid confusing users.
>
> Compile-tested only.
>
> Fixes: 75c487fcb69c ("platform/x86: intel-wmi-sbl-fw-update: Use bus-based WMI interface")
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
Thank you for your patch, I've applied this patch to my review-hans
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
I will include this patch in my next fixes pull-req to Linus
for the current kernel development cycle.
Regards,
Hans
> ---
> drivers/platform/x86/intel/wmi/sbl-fw-update.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/intel/wmi/sbl-fw-update.c b/drivers/platform/x86/intel/wmi/sbl-fw-update.c
> index 9cf5ed0f8dc2..040153ad67c1 100644
> --- a/drivers/platform/x86/intel/wmi/sbl-fw-update.c
> +++ b/drivers/platform/x86/intel/wmi/sbl-fw-update.c
> @@ -32,7 +32,7 @@ static int get_fwu_request(struct device *dev, u32 *out)
> return -ENODEV;
>
> if (obj->type != ACPI_TYPE_INTEGER) {
> - dev_warn(dev, "wmi_query_block returned invalid value\n");
> + dev_warn(dev, "wmidev_block_query returned invalid value\n");
> kfree(obj);
> return -EINVAL;
> }
> @@ -55,7 +55,7 @@ static int set_fwu_request(struct device *dev, u32 in)
>
> status = wmidev_block_set(to_wmi_device(dev), 0, &input);
> if (ACPI_FAILURE(status)) {
> - dev_err(dev, "wmi_set_block failed\n");
> + dev_err(dev, "wmidev_block_set failed\n");
> return -ENODEV;
> }
>
> --
> 2.39.2
>
prev parent reply other threads:[~2024-01-15 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 22:41 Armin Wolf
2024-01-07 0:00 ` Randy Dunlap
2024-01-08 10:52 ` Ilpo Järvinen
2024-01-15 12:41 ` Hans de Goede [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=fe0d8cc6-8217-4fa6-bf37-6ce76ae51192@redhat.com \
--to=hdegoede@redhat.com \
--cc=W_Armin@gmx.de \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jithu.joseph@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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®