From: Scott Wood <scottwood@freescale.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Should of_device_is_compatible() use strcmp() rather than strncasecmp()?
Date: Tue, 03 Jul 2007 17:15:11 -0500 [thread overview]
Message-ID: <468ACA6F.5010107@freescale.com> (raw)
In-Reply-To: <513A555F-5C7F-4FEF-B215-E0E683FEF9E1@kernel.crashing.org>
Segher Boessenkool wrote:
> Huh? Are you saying things are matching on substrings?
> That's even more wrong!
Yes, unfortunately. I tried getting the BRG frequency from the fsl,cpm
node and I got the fsl,cpm-enet node instead. :-P
ucc_geth requires device_type == network to avoid matching ucc_geth phy.
>> Does anything actually rely on this behavior?
>
>
> Yeah I'm pretty sure some things do. Those are bugs that
> need fixing. My plan was to print a big fat warning whenever
> a case-insensitive match wouldn't match when following the
> rules; I never got around to actually implementing that though.
> Maybe some day ;-)
How about a CONFIG_NOT_BROKEN_DEVICE_TREE that disables this and other
legacy stuff? If unset, warnings will be printed whenever broken things
are detected. Boards which need proper device tree parsing can select
the config option.
I'd prefer the other way around (CONFIG_BROKEN_DEVICE_TREE), but it'd
need to default y at first, and kconfig has no unselect command that I
can see...
-Scott
next prev parent reply other threads:[~2007-07-03 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 21:27 Should of_device_is_compatible() use strcmp() rather than strncasecmp()? Scott Wood
2007-07-03 21:54 ` Segher Boessenkool
2007-07-03 22:15 ` Scott Wood [this message]
2007-07-03 22:36 ` Olof Johansson
2007-07-03 22:33 ` Scott Wood
2007-07-03 22:52 ` Segher Boessenkool
2007-07-03 22:41 ` Segher Boessenkool
2007-07-04 3:28 ` Paul Mackerras
2007-07-04 12:09 ` Segher Boessenkool
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=468ACA6F.5010107@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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).