From: "Miguel Ojeda" <maxextreme@gmail.com>
To: akpm@osdl.org
Cc: "Stefan Richter" <stefanr@s5r6.in-berlin.de>,
"Randy Dunlap" <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18 V7] drivers: add lcd display support
Date: Sun, 1 Oct 2006 14:53:45 +0200 [thread overview]
Message-ID: <653402b90610010553p23819d2bsd7a07fabaee7ecf3@mail.gmail.com> (raw)
In-Reply-To: <20060930232445.59e8adf6.maxextreme@gmail.com>
On 10/1/06, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>
> It is as common as it is wrong. http://en.wikipedia.org/wiki/RAS_Syndrome
>
> A contraction like LCDisplay, like my suggested lcdisplay for the path
> name, is IMO not suitable for use in normal written language. Use it at
> most for path names where we contract words into one or would write
> lc-display or lc_display.
>
> Still wrong language.
>
> "LCD" and "LC display" are correct.
>
Sure it is wrong, the point is what is the best to understading. "LCD
display" seems better to me than just "LC display".
Maybe "drivers/lcdisplay" and "LCD" in common written places? Then we will have:
tristate "ks0108 LCD controller"
tristate "cfag12864b LCD"
That is the correct spelling, however, does it look good?
(I really don't know what is the best way to write it in english, I'm
spanish and here it is more common to say "LCD display").
next prev parent reply other threads:[~2006-10-01 12:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 23:24 Miguel Ojeda Sandonis
2006-10-01 12:53 ` Miguel Ojeda [this message]
2006-10-01 13:51 ` Stefan Richter
2006-10-01 14:25 ` Miguel Ojeda
2006-10-01 16:48 ` Stefan Richter
2006-10-01 17:58 ` Miguel Ojeda
2008-04-28 23:36 ` monitordelcd
2006-10-01 16:05 ` Valdis.Kletnieks
2006-10-01 16:17 ` Andreas Schwab
2006-10-01 17:33 ` Valdis.Kletnieks
2006-10-01 16:43 ` Randy Dunlap
2006-10-01 17:27 ` Alexander van Heukelum
2006-10-01 17:52 ` Miguel Ojeda
2006-10-01 18:25 ` Alexander van Heukelum
2006-10-01 16:53 ` Stefan Richter
2006-10-02 18:49 ` Andrew James Wade
2006-10-02 21:40 ` Miguel Ojeda
2006-10-03 0:06 ` Andrew James Wade
2006-10-03 12:55 ` Miguel Ojeda
2006-10-03 15:29 ` Randy Dunlap
2006-10-02 22:06 ` Alan Cox
2006-10-02 21:45 ` Miguel Ojeda
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=653402b90610010553p23819d2bsd7a07fabaee7ecf3@mail.gmail.com \
--to=maxextreme@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=stefanr@s5r6.in-berlin.de \
/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
Powered by JetHome