From: Grant Likely <grant.likely@linaro.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
nfont@linux.vnet.ibm.com
Subject: Re: of/dynamic: Fix test for PPC_PSERIES
Date: Fri, 05 Jun 2015 10:44:48 +0900 [thread overview]
Message-ID: <20150605014448.8C8C5C407BD@trevor.secretlab.ca> (raw)
In-Reply-To: <20150604105732.77DFE140273@ozlabs.org>
On Thu, 4 Jun 2015 20:57:32 +1000 (AEST)
, Michael Ellerman <mpe@ellerman.id.au>
wrote:
> On Thu, 2015-04-06 at 09:34:41 UTC, Geert Uytterhoeven wrote:
> > "IS_ENABLED(PPC_PSERIES)" always evaluates to false, as IS_ENABLED() is
> > supposed to be used with the full Kconfig symbol name, including the
> > "CONFIG_" prefix.
> >
> > Add the missing "CONFIG_" prefix to fix this.
> >
> > Fixes: a25095d451ece23b ("of: Move dynamic node fixups out of powerpc and into common code")
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > ---
>
> > Did this bug cause any breakage?
> > If yes, the fix should go to stable (for v3.17 and later).
>
> Yikes. Not that I've heard of. But it's reasonably new so possibly it's not hit
> distros that folks tend to run on those machines.
>
> I'm also not clear how it would break, it could be subtle and we've not noticed.
>
> Nathan might have more of an idea (on CC).
>
> On my machine here everything that has an ibm,phandle also has a linux,phandle,
> so we wouldn't hit that code path. But I'm not sure how representative that box
> is.
>
> cheers
Still, an obvious bug. I've picked it up and marked for stable.
g.
prev parent reply other threads:[~2015-06-05 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 9:34 [PATCH] " Geert Uytterhoeven
2015-06-04 10:57 ` Michael Ellerman
2015-06-05 0:43 ` Nathan Fontenot
2015-06-05 1:44 ` 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=20150605014448.8C8C5C407BD@trevor.secretlab.ca \
--to=grant.likely@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nfont@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®