From: Greg KH <gregkh@linuxfoundation.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
rafael@kernel.org, andriy.shevchenko@linux.intel.com,
hdegoede@redhat.com, jgg@ziepe.ca, saravanak@google.com,
keescook@chromium.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, abel.vesa@linaro.org,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH] devres: provide API devm_kstrndup
Date: Thu, 4 May 2023 17:58:10 +0900 [thread overview]
Message-ID: <2023050413-margin-devotedly-468d@gregkh> (raw)
In-Reply-To: <20230504075754.372780-1-peng.fan@oss.nxp.com>
On Thu, May 04, 2023 at 03:57:54PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> This patch introduces devm_kstrndup API so that the
> device's driver can allocate memory and copy string.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> drivers/base/devres.c | 28 ++++++++++++++++++++++++++++
> include/linux/device.h | 1 +
> 2 files changed, 29 insertions(+)
We can not add apis with no users, please submit this at the same time a
driver needs it.
And what driver would need to copy a string?
>
> diff --git a/drivers/base/devres.c b/drivers/base/devres.c
> index 5c998cfac335..87e2965e5bab 100644
> --- a/drivers/base/devres.c
> +++ b/drivers/base/devres.c
> @@ -963,6 +963,34 @@ char *devm_kstrdup(struct device *dev, const char *s, gfp_t gfp)
> }
> EXPORT_SYMBOL_GPL(devm_kstrdup);
>
> +/**
> + * devm_kstrndup - Allocate resource managed space and
> + * copy an existing string into that.
> + * @dev: Device to allocate memory for
> + * @s: the string to duplicate
> + * @max: max length to duplicate
> + * @gfp: the GFP mask used in the devm_kmalloc() call when allocating memory
> + * RETURNS:
> + * Pointer to allocated string on success, NULL on failure.
> + */
> +char *devm_kstrndup(struct device *dev, const char *s, size_t max, gfp_t gfp)
> +{
> + size_t len;
> + char *buf;
> +
> + if (!s)
> + return NULL;
> +
> + len = strnlen(s, max);
> + buf = devm_kmalloc(dev, len + 1, gfp);
> + if (buf) {
> + memcpy(buf, s, len);
> + buf[len] = '\0';
Why not use kstrndup() instead of copying the same logic here?
thanks,
greg k-h
next prev parent reply other threads:[~2023-05-04 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 7:57 [PATCH] devres: provide API devm_kstrndup Peng Fan (OSS)
2023-05-04 8:58 ` Greg KH [this message]
2023-05-04 8:59 ` Peng Fan
2023-05-04 9:08 ` Greg KH
2023-05-04 14:38 ` Andy Shevchenko
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=2023050413-margin-devotedly-468d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abel.vesa@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=jgg@ziepe.ca \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
--cc=tglx@linutronix.de \
/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.