From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] OF: base: match each node compatible against all given matches first
Date: Wed, 4 Dec 2013 15:04:59 +0100 [thread overview]
Message-ID: <20131204140457.GA2272@ulmo.nvidia.com> (raw)
In-Reply-To: <alpine.SOC.1.00.1312041506010.8902@math.ut.ee>
On Wed, Dec 04, 2013 at 03:08:39PM +0200, Meelis Roos wrote:
> > I added Meelis on Cc because he found a regression with my original
> > proposal (107a84e61cdd "of: match by compatible property first"). That
> > got later reverted in commit bc51b0c22ceb (Revert "of: match by
> > compatible property first"). Here's the commit message for reference:
> >
> > commit bc51b0c22ceb
> > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > Date: Tue Jul 10 12:49:32 2012 -0700
> >
> > Revert "of: match by compatible property first"
> >
> > This reverts commit 107a84e61cdd3406c842a0e4be7efffd3a05dba6.
> >
> > Meelis Roos reports a regression since 3.5-rc5 that stops Sun Fire V100
> > and Sun Netra X1 sparc64 machines from booting, hanging after enabling
> > serial console. He bisected it to commit 107a84e61cdd.
> >
> > Rob Herring explains:
> > "The problem is match combinations of compatible plus name and/or type
> > fail to match correctly. I have a fix for this, but given how late it
> > is for 3.5 I think it is best to revert this for now. There could be
> > other cases that rely on the current although wrong behavior. I will
> > post an updated version for 3.6."
> >
> > Bisected-and-reported-by: Meelis Roos <mroos@linux.ee>
> > Requested-by: Rob Herring <rob.herring@calxeda.com>
> > Cc: Thierry Reding <thierry.reding@avionic-design.de>
> > Cc: Grant Likely <grant.likely@secretlab.ca>
> > Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> >
> > So if Meelis still has access to the Sun Fire V100 and Sun Netra X1
> > machines that regressed last time around, it'd be great to get this
> > patch tested on them to verify that it indeed fixes the problem and
> > doesn't regress.
>
> OK, I had forgotten about that.
Yeah, I had always meant to come back to it, but that never quite
happened, so I'm all the more glad that Sebastian took over.
> Tested successfully on the same Sun Fire V100 and Sun Netra X1, on top
> of 3.13-rc2. The sunsu console is detected fine and I see no problem for
> now.
Excellent. Thanks for testing!
Rob, I guess this should be reasonable safe then to take for a spin in
linux-next?
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131204/910f6bdf/attachment.sig>
next prev parent reply other threads:[~2013-12-04 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 18:36 [PATCH] OF: base: match each node compatible against all given matches first Sebastian Hesselbarth
2013-12-02 12:03 ` Thierry Reding
2013-12-02 14:00 ` Rob Herring
2013-12-02 14:09 ` Sebastian Hesselbarth
2013-12-03 13:52 ` [PATCH v2] " Sebastian Hesselbarth
2013-12-03 20:14 ` Meelis Roos
2013-12-03 22:55 ` Sebastian Hesselbarth
2013-12-04 9:40 ` Thierry Reding
2013-12-04 13:08 ` Meelis Roos
2013-12-04 14:04 ` Thierry Reding [this message]
2013-12-04 19:23 ` Rob Herring
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=20131204140457.GA2272@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).