mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Miguel Ojeda <maxextreme@gmail.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18 V6] drivers: add lcd display support
Date: Sun, 1 Oct 2006 09:40:53 -0700	[thread overview]
Message-ID: <20061001094053.5d55bf06.rdunlap@xenotime.net> (raw)
In-Reply-To: <451F7A59.4020803@s5r6.in-berlin.de>

On Sun, 01 Oct 2006 10:20:41 +0200 Stefan Richter wrote:

> Randy Dunlap wrote:
> > On Sat, 30 Sep 2006 22:45:56 +0000 Miguel Ojeda wrote:
> ...
> >> 	tristate "CFAG12864B LCD Display"
> > 
> > That seems very common to me.
> 
> It is as common as it is wrong. http://en.wikipedia.org/wiki/RAS_Syndrome
> 
> ...
> >> LCDisplay??
> 
> 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.
> 
> > I would continue to use LCD display (small d).
> 
> Still wrong language.
> 
> "LCD" and "LC display" are correct.

whatever.
I've never heard anyone speak of or write about an LC display.

---
~Randy

  reply	other threads:[~2006-10-01 16:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-30 13:22 Miguel Ojeda Sandonis
2006-09-30 12:39 ` Jan-Benedict Glaw
2006-09-30 20:10   ` Miguel Ojeda
2006-09-30 19:35 ` Randy Dunlap
2006-09-30 21:36   ` Stefan Richter
2006-09-30 21:48     ` Randy Dunlap
2006-09-30 22:45       ` Miguel Ojeda
2006-09-30 22:52         ` Randy Dunlap
2006-10-01  8:20           ` Stefan Richter
2006-10-01 16:40             ` Randy Dunlap [this message]
2006-10-01 17:46               ` Stefan Richter
2006-10-01 18:04                 ` 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=20061001094053.5d55bf06.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxextreme@gmail.com \
    --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

all inboxes | Powered by JetHome®