From: bgat@billgatliff.com (Bill Gatliff)
To: linux-arm-kernel@lists.infradead.org
Subject: board/device file names, and machine names
Date: Tue, 02 Mar 2010 21:25:01 -0600 [thread overview]
Message-ID: <4B8DD68D.8000807@billgatliff.com> (raw)
In-Reply-To: <1267565398.8759.77.camel@c-dwalke-linux.qualcomm.com>
Daniel Walker wrote:
> I was wondering if you (or the list) had any suggestions for proper
> names to use in these two cases. Under mach-msm we have tons of devices
> that could be added, and it can sometimes be hard to isolate a sane
> name ..
>
Nobody outside of Google, HTC and/or Qualcomm will know the internal
names for these devices.
The majority of kernel.org developers don't work for Google, HTC and/or
Qualcomm. The internal names are therefore meaningless to the majority
of kernel.org developers.
Internet searches by the internal platform names will turn up nothing
useful.
I say use the product release names. But in board-nexusone.c add a
comment that says "this board is also known as: ...".
b.g.
--
Bill Gatliff
Embedded systems training and consulting
http://billgatliff.com
bgat at billgatliff.com
prev parent reply other threads:[~2010-03-03 3:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 21:29 board/device file names, and machine names Daniel Walker
2010-03-02 22:56 ` Brian Swetland
2010-03-02 23:29 ` Daniel Walker
2010-03-02 23:38 ` Brian Swetland
2010-03-03 3:42 ` Bill Gatliff
2010-03-03 3:36 ` Bill Gatliff
2010-03-03 8:00 ` Brian Swetland
2010-03-03 19:08 ` Theodore Tso
2010-03-03 19:22 ` Theodore Tso
2010-03-03 19:24 ` Russell King - ARM Linux
2010-03-02 23:51 ` Russell King - ARM Linux
2010-03-03 0:39 ` Daniel Walker
2010-03-03 0:47 ` Tim Bird
2010-03-03 0:52 ` Daniel Walker
2010-03-03 1:01 ` Brian Swetland
2010-03-03 3:52 ` Bill Gatliff
2010-03-03 8:42 ` Russell King - ARM Linux
2010-03-03 9:17 ` Pavel Machek
2010-03-03 9:47 ` Russell King - ARM Linux
2010-03-03 10:00 ` Pavel Machek
2010-03-03 10:08 ` Russell King - ARM Linux
2010-03-03 10:18 ` Pavel Machek
2010-03-03 10:18 ` Pavel Machek
2010-03-03 10:19 ` Russell King - ARM Linux
2010-03-03 10:19 ` Russell King - ARM Linux
2010-03-03 14:24 ` Pavel Machek
2010-03-03 14:24 ` Pavel Machek
2010-03-03 14:38 ` Daniel Walker
2010-03-03 22:08 ` Nicolas Pitre
2010-03-03 22:27 ` Brian Swetland
2010-03-03 3:25 ` Bill Gatliff [this message]
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=4B8DD68D.8000807@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=linux-arm-kernel@lists.infradead.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.