From: Michael Ellerman <michael@ellerman.id.au>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Fix legacy serial search for opb bus ports
Date: Wed, 06 Feb 2008 10:50:09 +1100 [thread overview]
Message-ID: <1202255409.11152.8.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20080205145008.GA5306@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
On Tue, 2008-02-05 at 09:50 -0500, Paul Gortmaker wrote:
> In message: [PATCH] Fix legacy serial search for opb bus ports
> on 05/02/2008 Michael Ellerman wrote:
>
> > The patch to legacy_serial.c (1a7507c7da2df6856e085e0fbb0c9ea8c12ac4e,
> > Reduce code duplication in legacy_serial, add UART parent types) changed
> > the semantics for opb ports from type = "opb" || compatible = "ibm,opb"
> > to type = "opb" && compatible = "ibm,opb".
>
> Ah. I'd originally coded it as an || -- but then Arnd suggested I
> condense it further by using of_match_node() -- which was a good idea,
> but that is where it accidentally changed to && without me catching it.
> Thanks for finding this, and sorry for the debug adventure (I know
> vanishing uarts isn't fun).
Yeah it's easy to confuse, I had to look at of_match_node() fairly
closely before I was convinced it was equivalent to &&. The bisect was
fairly painless actually, so no dramas.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-02-05 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 12:01 [PATCH] Fix legacy serial search for opb bus ports Michael Ellerman
2008-02-05 14:50 ` Paul Gortmaker
2008-02-05 23:50 ` Michael Ellerman [this message]
2008-02-06 0:08 ` Benjamin Herrenschmidt
2008-02-07 2:51 ` Arnd Bergmann
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=1202255409.11152.8.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paul.gortmaker@windriver.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).