From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Miguel Ojeda Sandonis <maxextreme@gmail.com>
Cc: 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 14:39:28 +0200 [thread overview]
Message-ID: <20060930123928.GV30245@lug-owl.de> (raw)
In-Reply-To: <20060930132253.8ccaa0ad.maxextreme@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
On Sat, 2006-09-30 13:22:53 +0000, Miguel Ojeda Sandonis <maxextreme@gmail.com> wrote:
> Patched files Index
> -------------------
> patching file drivers/Kconfig
> patching file drivers/lcddisplay/cfag12864b.c
> patching file drivers/lcddisplay/cfag12864b_image.h
> patching file drivers/lcddisplay/Kconfig
> patching file drivers/lcddisplay/ks0108.c
> patching file drivers/lcddisplay/lcddisplay.c
> patching file drivers/lcddisplay/Makefile
> patching file include/linux/lcddisplay.h
> patching file Documentation/lcddisplay/cfag12864b
> patching file Documentation/lcddisplay/lcddisplay
> patching file Documentation/ioctl-number.txt
AFAIK, the 'D' in LCD is already an abbreviation for "display", so
could we name it lcdisplay or something like that?
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-30 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 13:22 [PATCH 2.6.18 V6] drivers: add lcd display support Miguel Ojeda Sandonis
2006-09-30 12:39 ` Jan-Benedict Glaw [this message]
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
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=20060930123928.GV30245@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxextreme@gmail.com \
/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.