From: Kevin Hao <haokexin@gmail.com>
To: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: Grant Likely <grant.likely@linaro.org>,
Stephen N Chivers <schivers@csc.com.au>,
Rob Herring <robh+dt@kernel.org>, Kevin Hao <haokexin@gmail.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: [PATCH 0/2] of: fix a regression when trying to find the best compatible match
Date: Fri, 14 Feb 2014 13:22:44 +0800 [thread overview]
Message-ID: <1392355366-1445-1-git-send-email-haokexin@gmail.com> (raw)
Hi,
This fix a regression when trying to find the best compatible match. You can
find the detail of the issue reported by Stephen Chivers at:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-February/115278.html
I have made a patch to fix this previously.
http://patchwork.ozlabs.org/patch/319624/
This is another respin with the implementation suggested by Rob Herring.
Kevin Hao (2):
Revert "OF: base: match each node compatible against all given matches
first"
of: search the best compatible match first in __of_match_node()
drivers/of/base.c | 88 ++++++++++++++++++++++++++++++++++---------------------
1 file changed, 54 insertions(+), 34 deletions(-)
--
1.8.5.3
next reply other threads:[~2014-02-14 5:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 5:22 Kevin Hao [this message]
[not found] ` < 1392355366-1445-3-git-send-email-haokexin@gmail.com>
2014-02-14 5:22 ` [PATCH 1/2] Revert "OF: base: match each node compatible against all given matches first" Kevin Hao
2014-02-14 5:22 ` [PATCH 2/2] of: search the best compatible match first in __of_match_node() Kevin Hao
2014-02-14 15:53 ` Rob Herring
2014-02-14 16:19 ` Kumar Gala
2014-02-14 16:23 ` Kumar Gala
2014-02-15 5:19 ` Stephen N Chivers
2014-02-17 17:59 ` Grant Likely
2014-02-17 17:58 ` Grant Likely
2014-02-18 5:41 ` Kevin Hao
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=1392355366-1445-1-git-send-email-haokexin@gmail.com \
--to=haokexin@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=schivers@csc.com.au \
--cc=sebastian.hesselbarth@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;
as well as URLs for NNTP newsgroup(s).