From: "Miguel Ojeda" <maxextreme@gmail.com>
To: "Miguel Ojeda Sandonis" <maxextreme@gmail.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18 V6] drivers: add lcd display support
Date: Sat, 30 Sep 2006 20:10:24 +0000 [thread overview]
Message-ID: <653402b90609301310l54abf3a3y82f4f3e20d9f1394@mail.gmail.com> (raw)
In-Reply-To: <20060930123928.GV30245@lug-owl.de>
On 9/30/06, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>
> AFAIK, the 'D' in LCD is already an abbreviation for "display", so
> could we name it lcdisplay or something like that?
>
My first guess was "lcd" ("d" as display), but there were already
devices with such name. So I chose "display", as they are additional
small displays (LCD or not). However, people thought it was a very
common name. Then I chose "LCD Display". Such name is more expressive
(it is "a Display, LCD type") and doesn't makes trouble with new lcd
screens, or the "lcd" drivers, or...
I don't care really about the name with or without "double d". Can
someone else give his/her opinion about this?
Thank you,
Miguel Ojeda
> MfG, JBG
>
> --
> Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
> Signature of: The real problem with C++ for kernel modules is: the language just sucks.
> the second : -- Linus Torvalds
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFFHmWAHb1edYOZ4bsRAkdpAJ4g9+GPFYU4Y5W7JdGZXFDCmBDIggCfe6dk
> 3FbG+mcZQ+10MNkq5wC9J7w=
> =KzkJ
> -----END PGP SIGNATURE-----
>
>
>
next prev parent reply other threads:[~2006-09-30 20:10 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 [this message]
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
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=653402b90609301310l54abf3a3y82f4f3e20d9f1394@mail.gmail.com \
--to=maxextreme@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®