From: Guenter Roeck <linux@roeck-us.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Eugene Shalygin <eugene.shalygin@gmail.com>,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] hwmon: (asus-ec-sensors) fix a typo in asus_ec_probe()
Date: Sat, 5 Feb 2022 09:52:47 -0800 [thread overview]
Message-ID: <20220205175247.GA3075896@roeck-us.net> (raw)
In-Reply-To: <20220205092015.GA612@kili>
On Sat, Feb 05, 2022 at 12:20:15PM +0300, Dan Carpenter wrote:
> There is no such struct as "asus_ec_sensors", it was supposed to be
> "ec_sensors_data". This typo does not affect either build or runtime.
>
> Fixes: c4b1687d6897 ("hwmon: (asus-ec-sensors) add driver for ASUS EC")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied.
Thanks,
Guenter
> ---
> drivers/hwmon/asus-ec-sensors.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hwmon/asus-ec-sensors.c b/drivers/hwmon/asus-ec-sensors.c
> index 7285334c7d80..cb266ba30c97 100644
> --- a/drivers/hwmon/asus-ec-sensors.c
> +++ b/drivers/hwmon/asus-ec-sensors.c
> @@ -653,7 +653,7 @@ static int __init configure_sensor_setup(struct device *dev)
>
> static int __init asus_ec_probe(struct platform_device *pdev)
> {
> - struct asus_ec_sensors *state;
> + struct ec_sensors_data *state;
> int status = 0;
>
> state = devm_kzalloc(&pdev->dev, sizeof(struct ec_sensors_data),
prev parent reply other threads:[~2022-02-05 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 9:20 [PATCH] hwmon: (asus-ec-sensors) fix a typo in asus_ec_probe() Dan Carpenter
2022-02-05 9:59 ` Eugene Shalygin
2022-02-05 17:55 ` Guenter Roeck
2022-02-07 7:10 ` Dan Carpenter
2022-02-05 17:52 ` Guenter Roeck [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=20220205175247.GA3075896@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dan.carpenter@oracle.com \
--cc=eugene.shalygin@gmail.com \
--cc=jdelvare@suse.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-hwmon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.