From: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
To: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 3/4 v2] mtd/powerpc: Remove unused "device-width" property
Date: Tue, 7 Apr 2009 18:54:16 +0200 [thread overview]
Message-ID: <200904071854.16818.sr@denx.de> (raw)
In-Reply-To: <49DB8271.8050501-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
On Tuesday 07 April 2009, Scott Wood wrote:
> 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-ynQEQJNshbs@public.gmane.org>
> > CC: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
>
> The device tree describes the hardware, not what Linux happens to do
> with it at the moment.
>
> I'd rather keep it.
I find it rather confusing to "see" such bindings that are not supported. One
could expect something to happen/change after defining this property. So in
general I think adding unsupported properties to the Documentation is a bad
idea. But that's just my 2 cents. If the general opinion is to keep this
property, I'll keep it in of course.
Best regards,
Stefan
next prev parent reply other threads:[~2009-04-07 16:54 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
[not found] ` <49DB8271.8050501-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2009-04-07 16:54 ` Stefan Roese [this message]
[not found] ` <200904071854.16818.sr-ynQEQJNshbs@public.gmane.org>
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=200904071854.16818.sr@denx.de \
--to=sr-ynqeqjnshbs@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.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