From: David Gibson <david@gibson.dropbear.id.au>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Olof Johansson <olof@lixom.net>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/4] PowerPC: 440GRx Rainier DTS.
Date: Wed, 31 Oct 2007 13:56:13 +1100 [thread overview]
Message-ID: <20071031025613.GC7772@localhost.localdomain> (raw)
In-Reply-To: <20071030210917.42cfb88b@vader.jdub.homelinux.org>
On Tue, Oct 30, 2007 at 09:09:17PM -0500, Josh Boyer wrote:
> On Tue, 30 Oct 2007 20:56:51 -0500
> Olof Johansson <olof@lixom.net> wrote:
>
> > On Wed, Oct 31, 2007 at 10:08:05AM +1100, David Gibson wrote:
> > > On Tue, Oct 30, 2007 at 07:56:50PM +0300, Valentine Barshak wrote:
> > > > PowerPC 440GRx Rainier DTS.
> > > [snip]
> > > > + SDRAM0: sdram {
> > > > + device_type = "memory-controller";
> > >
> > > How many times do we need to say it...
> > >
> > > Don't make up random device_type values. This does not belong here.
> >
> > Maybe there should be something like checkpatch.pl that warns about
> > these kinds of things so people can check for it without getting flamed
> > first. :-)
I'd be gentler; except that I know Valentine has been active on this
list recently, so has almost certainly seen similar comments before.
> That's actually a decent idea. We could even have this thing that
> takes DTS files and processes them... oh wait.
>
> So why can't we make a whitelist of "allowed" device_types in DTC and
> make it whine about anything outside of that?
Well, that sort of thing is the idea for dtc to check, when it has
checks enabled anyway. Getting it so that it doesn't have too many
false positives is the tricky bit, as we've seen with some of the
existing checks (where "too many" is "almost any").
Patches welcome...
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-10-31 2:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 16:45 [PATCH 0/4] PowerPC: 440GRx Rainier board support Valentine Barshak
2007-10-30 16:56 ` [PATCH 1/4] PowerPC: 440GRx Rainier bootwrapper Valentine Barshak
2007-10-30 16:56 ` [PATCH 2/4] PowerPC: 440GRx Rainier DTS Valentine Barshak
2007-10-30 23:08 ` David Gibson
2007-10-31 1:56 ` Olof Johansson
2007-10-31 2:09 ` Josh Boyer
2007-10-31 2:56 ` David Gibson [this message]
2007-10-31 12:26 ` Valentine Barshak
2007-10-30 16:57 ` [PATCH 3/4] PowerPC: 440GRx Rainier board support Valentine Barshak
2007-10-30 19:59 ` Arnd Bergmann
2007-10-31 3:11 ` Stephen Rothwell
2007-10-31 12:23 ` Valentine Barshak
2007-10-30 17:00 ` [PATCH 4/4] PowerPC: 440GRx Rainier default config Valentine Barshak
2007-10-30 18:17 ` [PATCH 0/4] PowerPC: 440GRx Rainier board support Josh Boyer
2007-10-30 18:31 ` Valentine Barshak
2007-10-30 20:16 ` Josh Boyer
2007-10-31 12:21 ` Valentine Barshak
2007-10-31 12:59 ` Josh Boyer
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=20071031025613.GC7772@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=jwboyer@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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).