From: Scott Wood <scottwood@freescale.com>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 3/4 v2] mtd/powerpc: Remove unused "device-width" property
Date: Tue, 07 Apr 2009 11:42:25 -0500 [thread overview]
Message-ID: <49DB8271.8050501@freescale.com> (raw)
In-Reply-To: <1239093575-12147-1-git-send-email-sr@denx.de>
Stefan Roese wrote:
> This property is unused. It's not handled as all by the physmap_of
> driver. So let's remove it from the documentation.
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> CC: Grant Likely <grant.likely@secretlab.ca>
The device tree describes the hardware, not what Linux happens to do
with it at the moment.
I'd rather keep it.
-Scott
next prev parent reply other threads:[~2009-04-07 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 8:39 [PATCH 3/4 v2] mtd/powerpc: Remove unused "device-width" property Stefan Roese
2009-04-07 16:42 ` Scott Wood [this message]
2009-04-07 16:54 ` Stefan Roese
2009-04-12 6:01 ` 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=49DB8271.8050501@freescale.com \
--to=scottwood@freescale.com \
--cc=devicetree-discuss@ozlabs.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.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).