From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: Juergen Beisert <j.beisert@pengutronix.de>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] i.MX Framebuffer: Use iowrite/ioread instead of direct pointer deref
Date: Wed, 20 Aug 2008 22:23:40 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0808202221590.16983@anakin> (raw)
In-Reply-To: <20080820194246.0dc9a589.krzysztof.h1@poczta.fm>
On Wed, 20 Aug 2008, Krzysztof Helt wrote:
> On Wed, 20 Aug 2008 18:31:09 +0200
> Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Wed, Aug 20, 2008 at 05:31:59PM +0200, Krzysztof Helt wrote:
> > > On Tue, 19 Aug 2008 17:06:41 +0200
> > > Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > > > +#define DRIVER_NAME "imx-fb"
> > > > +
> > >
> > > All constants below should really be put into the imxfb.h. There is already such a file.
> >
> > AFAIK the-new-beautiful-way is not to have these header files next to
> > the .c files at all and put this stuff into the .c file. So maybe it's
> > better to move the rest of imxfb.h here aswell.
>
> I was not aware about "the-new-beautiful-way". I am just curious about this.
> Normally, the headers for frame buffers are located at include/video.
>
> It can stay this way (no header) if you insist.
If the header file is included by a single source file only, it doesn't
make much sense to have the separate header file.
include/video/ is for header files that are included by multiple source
files, some outside drivers/video/.
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 the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
next prev parent reply other threads:[~2008-08-20 20:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 15:06 i.MX Framebuffer patches Sascha Hauer
2008-08-19 15:06 ` [PATCH] i.MX Framebuffer: remove gpio setup function Sascha Hauer
2008-08-20 15:52 ` Krzysztof Helt
2008-08-19 15:06 ` [PATCH] i.MX Framebuffer: Use iowrite/ioread instead of direct pointer deref Sascha Hauer
2008-08-20 15:31 ` Krzysztof Helt
2008-08-20 16:31 ` Sascha Hauer
2008-08-20 17:42 ` Krzysztof Helt
2008-08-20 20:23 ` Geert Uytterhoeven [this message]
2008-08-19 15:06 ` [PATCH] i.MX Framebuffer: Cleanup Coding style Sascha Hauer
2008-08-20 15:35 ` Krzysztof Helt
2008-08-20 16:15 ` Sascha Hauer
2008-08-20 17:35 ` Krzysztof Helt
2008-08-21 7:13 ` Sascha Hauer
2008-08-19 15:06 ` [PATCH] i.MX Framebuffer: rename imxfb_mach_info to imx_fb_platform_data Sascha Hauer
2008-08-20 15:51 ` Krzysztof Helt
2008-08-20 16:18 ` Sascha Hauer
-- strict thread matches above, loose matches on Subject: below --
2008-09-02 11:24 i.MX framebuffer patches Sascha Hauer
2008-09-02 11:24 ` [PATCH] i.MX Framebuffer: Use iowrite/ioread instead of direct pointer deref Sascha Hauer
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.0808202221590.16983@anakin \
--to=geert@linux-m68k.org \
--cc=j.beisert@pengutronix.de \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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