From: David Gibson <david@gibson.dropbear.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Li Yang <leoli@freescale.com>, paulus@samba.org
Subject: Re: [PATCH 2/2] Add local bus device nodes to MPC837xMDS device trees.
Date: Tue, 11 Mar 2008 10:54:29 +1100 [thread overview]
Message-ID: <20080310235429.GC11559@localhost.localdomain> (raw)
In-Reply-To: <9f7d0248e911f6fa1a2d4292c96ef72e@kernel.crashing.org>
On Fri, Mar 07, 2008 at 04:39:30AM +0100, Segher Boessenkool wrote:
> > This isn't a problem with this device tree, but it's probably time we
> > started establishing some conventional generic names for nand flash
> > and board-control devices.
> >
> > So, to start the ball rolling, I've seen several names for nand flash
> > nodes, I'd suggest we standardise on "nand-flash".
>
> What's wrong with the already well-established generic name "flash"?
I was concerned that using "flash" for both NOR flash (which it
already is) and NAND flash might be unwise. I am quite open to being
convinced otherwise, though.
> > I've seen several variants for board control devices (cpld, bcsr,
> > fpga, etc.) I suggest we standardise on "board-control"
>
> Fine with me, but it's very vague (hard to avoid though).
Yes.
--
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:[~2008-03-10 23:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 10:42 [PATCH 2/2] Add local bus device nodes to MPC837xMDS device trees Li Yang
2008-03-07 0:27 ` David Gibson
2008-03-07 3:39 ` Segher Boessenkool
2008-03-10 23:54 ` David Gibson [this message]
2008-03-11 0:43 ` Arnd Bergmann
2008-03-11 1:32 ` David Gibson
2008-03-11 18:43 ` Segher Boessenkool
2008-03-07 14:35 ` Kumar Gala
2008-03-07 18:24 ` Segher Boessenkool
2008-03-08 0:37 ` David Gibson
2008-03-07 14:46 ` Kumar Gala
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=20080310235429.GC11559@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.