From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: jic23@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] counter: Set counter device name
Date: Thu, 3 Feb 2022 10:00:53 +0100 [thread overview]
Message-ID: <20220203090053.oki5ts4c2gdpi2c6@pengutronix.de> (raw)
In-Reply-To: <20220203073459.90093-1-vilhelm.gray@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1736 bytes --]
On Thu, Feb 03, 2022 at 04:34:59PM +0900, William Breathitt Gray wrote:
> Naming the counter device provides a convenient way to identify it in
> devres_log events and similar situations. This patch names the counter
> device by combining the prefix "counter" with the counter device's
> unique ID.
>
> Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
> ---
> drivers/counter/counter-core.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/counter/counter-core.c b/drivers/counter/counter-core.c
> index 7e0957eea094..2ebd9adf0bd2 100644
> --- a/drivers/counter/counter-core.c
> +++ b/drivers/counter/counter-core.c
> @@ -22,6 +22,8 @@
> #include "counter-chrdev.h"
> #include "counter-sysfs.h"
>
> +#define COUNTER_NAME "counter"
> +
> /* Provides a unique ID for each counter device */
> static DEFINE_IDA(counter_ida);
>
> @@ -104,6 +106,10 @@ struct counter_device *counter_alloc(size_t sizeof_priv)
> goto err_ida_alloc;
> dev->id = err;
>
> + err = dev_set_name(dev, COUNTER_NAME "%d", dev->id);
> + if (err)
> + goto err_dev_set_name;
> +
> mutex_init(&counter->ops_exist_lock);
> dev->type = &counter_device_type;
> dev->bus = &counter_bus_type;
> @@ -119,6 +125,9 @@ struct counter_device *counter_alloc(size_t sizeof_priv)
>
> err_chrdev_add:
>
> + kfree(dev_name(dev));
> +err_dev_set_name:
> +
I think this is wrong as kobject_cleanup frees the name.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-03 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 7:34 William Breathitt Gray
2022-02-03 9:00 ` Uwe Kleine-König [this message]
2022-02-04 6:41 ` William Breathitt Gray
2022-02-04 7:43 ` Uwe Kleine-König
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=20220203090053.oki5ts4c2gdpi2c6@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vilhelm.gray@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
all inboxes | Powered by JetHome®