From: Mark Rutland <mark.rutland@arm.com>
To: Rob Herring <robherring2@gmail.com>, Lee Jones <lee.jones@linaro.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linaro Patches <patches@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 3/3] of: Handle memory@0 node on PPC32 only
Date: Wed, 23 Apr 2014 11:35:36 +0100 [thread overview]
Message-ID: <20140423103536.GC30036@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <CAL_JsqJTMWKh3gsv0TnRap82+7BM4XaT4ZAWkQmyfvzTqOq12g@mail.gmail.com>
Hi,
> > diff --git a/drivers/of/Kconfig b/drivers/of/Kconfig
> > index 889005f..230c747 100644
> > --- a/drivers/of/Kconfig
> > +++ b/drivers/of/Kconfig
> > @@ -77,4 +77,7 @@ config OF_RESERVED_MEM
> > help
> > Helpers to allow for reservation of memory regions
> >
> > +config OF_MEMORY_AT_0_QUIRK
> > + def_bool n
>
> I do not like this because it would not scale to many quirks. As I
> said,, my preference here would be to just add a WARN.
I would very much like to be able to remove the quirk entirely for arm64
if possible, which would require more than the addition of a WARN.
> The other option is get approval to break compatibility on the ST
> platform. It may not be a concern on certain platforms.
Lee, would you be able to provide an answer either way so we can get
the discussion moving?
Cheers,
Mark.
next prev parent reply other threads:[~2014-04-23 10:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 17:41 [PATCH 0/3] of: dts: enable memory@0 quirk for PPC32 only Leif Lindholm
2014-04-17 17:42 ` [PATCH 3/3] of: Handle memory@0 node on " Leif Lindholm
2014-04-18 8:04 ` Geert Uytterhoeven
2014-04-18 12:59 ` Leif Lindholm
2014-04-18 13:11 ` Geert Uytterhoeven
2014-04-21 12:56 ` Rob Herring
2014-04-23 10:35 ` Mark Rutland [this message]
2014-04-22 13:35 ` Grant Likely
2014-04-23 10:45 ` Mark Rutland
2014-04-23 11:14 ` Geert Uytterhoeven
2014-04-23 13:10 ` Grant Likely
2014-04-24 9:26 ` Leif Lindholm
2014-05-15 14:59 ` Grant Likely
2014-04-18 0:43 ` [PATCH 0/3] of: dts: enable memory@0 quirk for " Rob Herring
2014-04-18 12:48 ` Leif Lindholm
2014-04-18 15:37 ` Rob Herring
2014-04-18 20:13 ` Leif Lindholm
2014-04-18 21:28 ` Rob Herring
2014-04-19 0:36 ` Leif Lindholm
2014-04-22 13:08 ` Grant Likely
2014-04-22 14:05 ` Leif Lindholm
2014-04-23 13:15 ` Grant Likely
2014-04-23 17:25 ` Leif Lindholm
2014-04-23 13:17 ` Grant Likely
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=20140423103536.GC30036@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=grant.likely@linaro.org \
--cc=lee.jones@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=patches@linaro.org \
--cc=robherring2@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).