devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	Shawn Guo <shawnguo@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] ARM: dts: imx: Pass 'chosen' and 'memory' nodes
Date: Thu, 19 Jan 2017 12:35:40 -0200	[thread overview]
Message-ID: <CAOMZO5AdgM9eFnerLRdYxwE7gsOE5OvkWs6rCR4zta1XmXHj1A@mail.gmail.com> (raw)
In-Reply-To: <20170119141335.kpbrbpbwaovnijjv@pengutronix.de>

Hi Uwe,

On Thu, Jan 19, 2017 at 12:13 PM, Uwe Kleine-König
<u.kleine-koenig@pengutronix.de> wrote:

> Would it be nice to add a comment about why this was added? Something to
> prevent a cleanup like "remove empty nodes and invalid memory
> configurations".

Do you mean something like this?

/* "chosen" and "memory" nodes are mandatory */
chosen {};
memory { device_type = "memory"; reg = <0 0>; };

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2017-01-19 14:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 14:02 [PATCH v2] ARM: dts: imx: Pass 'chosen' and 'memory' nodes Fabio Estevam
2017-01-19 14:13 ` Uwe Kleine-König
2017-01-19 14:35   ` Fabio Estevam [this message]
     [not found]     ` <CAOMZO5AdgM9eFnerLRdYxwE7gsOE5OvkWs6rCR4zta1XmXHj1A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-19 14:46       ` Uwe Kleine-König
2017-01-19 14:56         ` Russell King - ARM Linux
2017-01-19 15:57           ` Fabio Estevam
2017-01-19 16:14           ` Uwe Kleine-König
     [not found]             ` <20170119161441.jcctgig7np4v7sam-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-01-25 21:13               ` Frank Rowand
     [not found]                 ` <588914F3.7050909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-25 22:46                   ` Rob Herring
     [not found]                     ` <CAL_JsqL4+OZo0JTU8gnTEHxqNgNoBRnuHr1i99n72BKG30V9Eg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-26  0:30                       ` Frank Rowand
2017-01-30 18:54                 ` Russell King - ARM Linux
     [not found]                   ` <20170130185444.GF27312-l+eeeJia6m9URfEZ8mYm6t73F7V6hmMc@public.gmane.org>
2017-01-30 19:07                     ` Fabio Estevam
2017-01-30 19:47                     ` Uwe Kleine-König
2017-02-01 13:30                     ` Stefan Wahren
2017-02-06 10:49                       ` Stefan Wahren
     [not found]                         ` <13787b59-6bfc-d020-9853-ae37074009dc-eS4NqCHxEME@public.gmane.org>
2017-02-06 11:05                           ` Fabio Estevam
2017-02-07 15:19                             ` 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=CAOMZO5AdgM9eFnerLRdYxwE7gsOE5OvkWs6rCR4zta1XmXHj1A@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=javier@osg.samsung.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=shawnguo@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).