From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Li Yang <leoli@freescale.com>,
paulus@samba.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 2/2] Add local bus device nodes to MPC837xMDS device trees.
Date: Fri, 7 Mar 2008 19:24:10 +0100 [thread overview]
Message-ID: <3e5545630948f7bb2a2a6e103eb4ed10@kernel.crashing.org> (raw)
In-Reply-To: <A984ECC2-9094-4045-B49E-95D924E6AAD2@kernel.crashing.org>
>> I've seen several variants for board control devices (cpld, bcsr,
>> fpga, etc.) I suggest we standardise on "board-control"
>
> I don't see any reason for this. If I have a cpld or fpga why not
> just call it that. I don't see what calling it 'board-control' gets
> us. There may be non-board control functionality in an fpga than what
> do we call it?
Good point. Also, it is important to keep in mind that the "name" is
meant for human consumption only, so while it is important to use some
consistent naming (to not confuse the user), there should be quite some
leeway here.
Segher
next prev parent reply other threads:[~2008-03-07 18:24 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
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 [this message]
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=3e5545630948f7bb2a2a6e103eb4ed10@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=galak@kernel.crashing.org \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).