From: Grant Likely <grant.likely@secretlab.ca>
To: Stuart Yoder <stuart.yoder@freescale.com>,linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH][v2] fix of_flat_dt_is_compatible to match the full compatible string
Date: Sat, 24 Jul 2010 13:34:29 -0600 [thread overview]
Message-ID: <c1d83b47-1185-4b51-b35f-10b914e1515e@email.android.com> (raw)
In-Reply-To: <1279910564-17887-1-git-send-email-stuart.yoder@freescale.com>
"Stuart Yoder" <stuart.yoder@freescale.com> wrote:
>From: Stuart Yoder <stuart.yoder@freescale.com>
>
>With the previous string comparison, a device tree
>compatible of "foo-bar" would match as compatible
>with a driver looking for "foo".
>
>Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
Hi Stewart.
Patch looks good. I'll test it this afternoon.
However, please remember to cc: me and devicetree-discuss if you want patches picked up remotely quickly (I know, I'm slow anyway, but I'm even slower when I don't see something. I only came across this one by chance.)
g.
>---
> drivers/of/fdt.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
>diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
>index dee4fb5..28c0c2b 100644
>--- a/drivers/of/fdt.c
>+++ b/drivers/of/fdt.c
>@@ -169,7 +169,7 @@ int __init of_flat_dt_is_compatible(unsigned long node, const char *compat)
> if (cp == NULL)
> return 0;
> while (cplen > 0) {
>- if (strncasecmp(cp, compat, strlen(compat)) == 0)
>+ if (!strcasecmp(cp, compat))
> return 1;
> l = strlen(cp) + 1;
> cp += l;
>--
>1.6.2.5
>
>
>_______________________________________________
>Linuxppc-dev mailing list
>Linuxppc-dev@lists.ozlabs.org
>https://lists.ozlabs.org/listinfo/linuxppc-dev
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
prev parent reply other threads:[~2010-07-24 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 18:42 [PATCH][v2] fix of_flat_dt_is_compatible to match the full compatible string Stuart Yoder
2010-07-24 19:34 ` Grant Likely [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=c1d83b47-1185-4b51-b35f-10b914e1515e@email.android.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stuart.yoder@freescale.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;
as well as URLs for NNTP newsgroup(s).