From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Cc: Andrew Morton <akpm@osdl.org>, Bryan Wu <bryan.wu@analog.com>,
Michael Hennerich <michael.hennerich@analog.com>
Subject: Re: [PATCH 07/17] bf54x-lq043fb: Framebuffer driver for Blackfin BF54x framebuffer device driver
Date: Sat, 29 Sep 2007 11:17:42 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709291116460.10965@anakin> (raw)
In-Reply-To: <46FDAAD1.6070700@gmail.com>
On Sat, 29 Sep 2007, Antonino A. Daplas wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
>
> Blackfin BF54x framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
>
> [adaplas]
> Add 'fb' suffix to driver name.
Won't work though if you forget to rename the actual source file:
> drivers/video/bf54x-lq043.c | 786 +++++++++++++++++++++++++
> +obj-$(CONFIG_FB_BF54X_LQ043) += bf54x-lq043fb.o
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-29 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 1:30 [PATCH 07/17] bf54x-lq043fb: Framebuffer driver for Blackfin BF54x framebuffer device driver Antonino A. Daplas
2007-09-29 9:17 ` Geert Uytterhoeven [this message]
2007-09-30 1:06 ` [PATCH 07/17 RESEND] " Antonino A. Daplas
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=Pine.LNX.4.64.0709291116460.10965@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@osdl.org \
--cc=bryan.wu@analog.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=michael.hennerich@analog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).