From: Leif Lindholm <leif.lindholm@linaro.org>
To: Grant Likely <grant.likely@secretlab.ca>,
Mark Rutland <mark.rutland@arm.com>
Cc: Rob Herring <robherring2@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linaro Patches <patches@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 0/3] of: dts: enable memory@0 quirk for PPC32 only
Date: Wed, 23 Apr 2014 18:25:23 +0100 [thread overview]
Message-ID: <20140423172523.GM5904@bivouac.eciton.net> (raw)
In-Reply-To: <20140423131508.6E53BC408D2@trevor.secretlab.ca>
On Wed, Apr 23, 2014 at 02:15:08PM +0100, Grant Likely wrote:
> > The reason for me doing that is because we (including you) agreed at
> > the discussion held during LCU13 that this was the safest way of
> > preventing "mischief" like userland trying to read information from
> > /proc/device-tree...
>
> I'm not the most consistent of people. I often change my mind and then
> have no recollection of ever thinking differently.
And that is fine, but you were not the only person agreeing.
> Userland reading from /proc/device-tree isn't so much a problem, but
> kernel drivers doing it might be.
>
> But, regardless of whether or not the stub clears out the memory
> nodes, it is still I think good practice for the kernel to make the
> decision to ignore memory nodes, and not rely on them being cleared
> correctly.
I also remember you saying that relaxing restrictions later on is a lot
easier than tightening them. On that basis, can we please get the UEFI
set merged before we start redefining the stub/kernel protocol which was
agreed at LCU (November last year) after spending a month or two trying
to get sufficient number of interested parties in the same room?
/
Leif
next prev parent reply other threads:[~2014-04-23 17:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 17:41 Leif Lindholm
2014-04-17 17:41 ` [PATCH 1/3] arm: dts: add device_type="memory" for ste-ccu8540 Leif Lindholm
2014-04-22 7:39 ` Lee Jones
2014-04-22 13:09 ` Grant Likely
2014-04-22 13:26 ` Linus Walleij
2014-05-15 14:50 ` Grant Likely
2014-04-17 17:42 ` [PATCH 2/3] mips: dts: add device_type="memory" where missing Leif Lindholm
2014-04-18 17:16 ` John Crispin
2014-04-22 13:13 ` Grant Likely
2014-05-15 14:50 ` Grant Likely
2014-04-17 17:42 ` [PATCH 3/3] of: Handle memory@0 node on PPC32 only 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
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 [this message]
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=20140423172523.GM5904@bivouac.eciton.net \
--to=leif.lindholm@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--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
all inboxes | Powered by JetHome®