From: Rob Herring <robh@kernel.org>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: replace strcmp_suffix() with strends()
Date: Mon, 15 Dec 2025 13:28:54 -0600 [thread overview]
Message-ID: <20251215192854.GA3162398-robh@kernel.org> (raw)
In-Reply-To: <20251215154809.70041-1-bartosz.golaszewski@oss.qualcomm.com>
On Mon, Dec 15, 2025 at 04:48:09PM +0100, Bartosz Golaszewski wrote:
> string.h now provides strends() which fulfills the same role as the
> locally implemented strcmp_suffix(). Use it in of/property.c.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
> ---
> drivers/of/property.c | 15 ++-------------
> 1 file changed, 2 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/of/property.c b/drivers/of/property.c
> index 4e3524227720a..0a68223954f09 100644
> --- a/drivers/of/property.c
> +++ b/drivers/of/property.c
> @@ -1294,17 +1294,6 @@ static struct device_node *parse_##fname(struct device_node *np, \
> return parse_prop_cells(np, prop_name, index, name, cells); \
> }
>
> -static int strcmp_suffix(const char *str, const char *suffix)
> -{
> - unsigned int len, suffix_len;
> -
> - len = strlen(str);
> - suffix_len = strlen(suffix);
> - if (len <= suffix_len)
> - return -1;
> - return strcmp(str + len - suffix_len, suffix);
> -}
> -
> /**
> * parse_suffix_prop_cells - Suffix property parsing function for suppliers
> *
> @@ -1331,7 +1320,7 @@ static struct device_node *parse_suffix_prop_cells(struct device_node *np,
> {
> struct of_phandle_args sup_args;
>
> - if (strcmp_suffix(prop_name, suffix))
> + if (strends(prop_name, suffix))
> return NULL;
>
> if (of_parse_phandle_with_args(np, prop_name, cells_name, index,
> @@ -1416,7 +1405,7 @@ DEFINE_SUFFIX_PROP(gpio, "-gpio", "#gpio-cells")
> static struct device_node *parse_gpios(struct device_node *np,
> const char *prop_name, int index)
> {
> - if (!strcmp_suffix(prop_name, ",nr-gpios"))
> + if (!strends(prop_name, ",nr-gpios"))
Don't you need to negate these?
next prev parent reply other threads:[~2025-12-15 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 15:48 [PATCH] of: replace strcmp_suffix() with strends() Bartosz Golaszewski
2025-12-15 19:28 ` Rob Herring [this message]
2025-12-16 7:45 ` Bartosz Golaszewski
2025-12-16 12:57 ` Rob Herring
2025-12-16 14:53 ` Bartosz Golaszewski
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=20251215192854.GA3162398-robh@kernel.org \
--to=robh@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).