linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Thomas H?henleitner <th@visuelle-maschinen.de>
To: James Simmons <jsimmons@acsu.buffalo.edu>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Adrian Cox <apc@agelectronics.co.uk>,
	Linux Frame Buffer Device Development
	<linux-fbdev@vuser.vu.union.edu>,
	LinuxPPC-Dev <linuxppc-dev@lists.linuxppc.org>
Subject: name space pollution Was Re: [linux-fbdev] CTFB 0.30 now availiable (CT65554...CT69000)
Date: Tue, 20 Jun 2000 11:03:42 +0200	[thread overview]
Message-ID: <00062011283507.10856@iris> (raw)
In-Reply-To: <Pine.LNX.4.10.10006191510001.455-100000@maxwell.futurevision.com>


Am Mon, 19 Jun 2000 schrieb James Simmons:

> I got it now thanks to Geert. You have alot of files for ctfb.
>

It's a matter of taste. A file overview is in ctfb_README. And no big deal to
merge them into one monolitc block if it should go into the kernel sources.

By the way I have here a question:

If we have several submodules as parts of a framebuffer we have some symbols
within the namespace of this framebuffer. When we compile it as a separate
module for modprobe there is no problem. But when we compile it as part of the
kernel these frambuffer specific symbols are polluting the kernel namespace. Is
there an elegant way to make the framebuffer specific symbols invisible for the
kernel after we have  our xxxfb.o?

Thomas

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-06-20  9:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-16  9:31 copy_from_user in drivers/video/fbmem.c Adrian Cox
2000-06-16 11:14 ` Geert Uytterhoeven
2000-06-16 14:04   ` [linux-fbdev] " James Simmons
2000-06-19 10:15   ` CTFB 0.30 now availiable (CT65554...CT69000) Thomas H?henleitner
2000-06-19 11:11     ` Adrian Cox
2000-06-19 17:31       ` Thomas H?henleitner
2000-06-19 14:12     ` [linux-fbdev] " James Simmons
2000-06-19 14:28       ` Geert Uytterhoeven
2000-06-19 14:41         ` James Simmons
2000-06-19 17:27         ` Thomas H?henleitner
2000-06-19 19:11           ` James Simmons
2000-06-20  9:03             ` Thomas H?henleitner [this message]
2000-06-20 23:40               ` name space pollution Was " James Simmons

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=00062011283507.10856@iris \
    --to=th@visuelle-maschinen.de \
    --cc=apc@agelectronics.co.uk \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@acsu.buffalo.edu \
    --cc=linux-fbdev@vuser.vu.union.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).