linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Thomas Pfaff <tpfaff@pcs.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com
Subject: Re: [PATCH] [Resend] fbcon : fix color generation for monochrome framebuffer
Date: Fri, 1 Feb 2008 14:38:15 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0802011426140.18111@anakin> (raw)
In-Reply-To: <Pine.LNX.4.64.0802011353430.5628@lxtpfaff.pcs.ditec.de>

On Fri, 1 Feb 2008, Thomas Pfaff wrote:
> On Fri, 1 Feb 2008, Geert Uytterhoeven wrote:
> > On Fri, 1 Feb 2008, Thomas Pfaff wrote:
> > > On Thu, 31 Jan 2008, Andrew Morton wrote:
> > > > On Mon, 28 Jan 2008 11:03:38 +0100 (CET)
> > > If the functions should be deinlined someone should decide where to put them. 
> > > Since they must be exported i would avoid to put them into fbcon.c, this would 
> > > lead to cross dependencies.
> > > I would suggest to put the prototype into <linux/fb.h> and the definition into 
> > > fbcmap.c instead, but i am unsure whether they really belong there.
> > 
> > General note: functions in header files must be inline, else you get
> > multiple definitions of the same symbol.
> 
> Of course you are right but this does not answer my question:
> Where should i put a mono_col / attr_col_ec if they must be deinlined ?

Sorry, I misunderstood. I thought you meant the macros that Andrew
wanted to be turned into functions.

> My suggestion is a fb_mono_col / fb_attr_col_ec in fbcmap.c.

As they're used by fbcon only, not by fbdev, I'd suggest fbcon.c.

pmag-aa-fb.c is the only other user, but it's broken anyway because it
still uses the 2.4.x fbdev API.

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 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-02-01 13:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 10:03 [PATCH] [Resend] fbcon : fix color generation for monochrome framebuffer Thomas Pfaff
2008-01-31 22:07 ` Andrew Morton
2008-01-31 22:18   ` Andrew Morton
2008-02-01  8:02   ` Geert Uytterhoeven
2008-02-01 11:58   ` Thomas Pfaff
2008-02-01 12:24     ` Geert Uytterhoeven
2008-02-01 13:01       ` Thomas Pfaff
2008-02-01 13:38         ` Geert Uytterhoeven [this message]
2008-02-01 13:55           ` Thomas Pfaff

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.0802011426140.18111@anakin \
    --to=geert@linux-m68k.org \
    --cc=adaplas@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=tpfaff@pcs.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).