From: "Miguel Ojeda" <maxextreme@gmail.com>
To: "Randy Dunlap" <rdunlap@xenotime.net>
Cc: "Stefan Richter" <stefanr@s5r6.in-berlin.de>,
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 22:45:56 +0000 [thread overview]
Message-ID: <653402b90609301545y2d4f162dq824ac360149fc0a7@mail.gmail.com> (raw)
In-Reply-To: <20060930144830.eba63268.rdunlap@xenotime.net>
Randy, I'm testing right now the V7 of the driver after fixing all
your mistakes found. Thank you for your deep work: the sharing of the
buffer was a very good point. Finally I allocated both 2 (the bigger
and the smaller one at the initialization).
In a few minutes I will send the V7 patch.
About "lcdisplay":
On 9/30/06, Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Sat, 30 Sep 2006 23:36:44 +0200 Stefan Richter wrote:
>
> > ...
> > >> patching file drivers/lcddisplay/cfag12864b.c
> > ...
> >
> > What does the D in LCD stand for? I suggest this is named
> > drivers/lcdisplay/ instead.
>
> Yes, someone else mentioned that too.
> It does mean Display.
> not a big deal to me in this age of acronyms.
>
Well, I can rename it, but there is a problem:
How should I write the name in other places?
I mean, for example, in Kconfig:
tristate "KS0108 LCD Controller"
if the ks0108 is a LCD controller, then
tristate "CFAG12864B LCD Display"
should be the right way to write it?
tristate "CFAG12864B LCDisplay"
seems so ugly to me. Is it? Remember, this applies for all the other
places in the documentation / source code / ...
IMHO it seems better as LCD Display. Yeah, drivers/lcdisplay/ would be
nice, but I don't think the same about other places:
LCD Controller.
LCDisplay??
next prev parent reply other threads:[~2006-09-30 22:45 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 [this message]
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=653402b90609301545y2d4f162dq824ac360149fc0a7@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
all inboxes | Powered by JetHome®