From: GOTO Masanori <gotom@debian.or.jp>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: gotom@debian.or.jp, dan@debian.org
Subject: Re: [PATCH] don't export fb.h internal structure to userland
Date: Thu, 06 Nov 2003 00:55:13 +0900 [thread overview]
Message-ID: <80isly95em.wl@oris.opensource.jp> (raw)
In-Reply-To: <80n0bc913h.wl@oris.opensource.jp>
Hi,
This patch one more fix for linux/fb.h, to move asm/io.h into
__KERNEL__. It should also be internal of __KERNEL__. This patch can
be applied after my previous linux/fb.h patch is applied.
All my 3 patches are reported by debian package build (because the
latest debian unstable distribution /usr/include/linux/* uses the
latest linux kernel headers), and many userland applications currently
can't build. So please apply these patches for your tree.
This patch from Daniel Jacobowitz <dan@debian.org>.
Regards,
-- gotom
--- include/linux/fb.h 2003-11-04 14:15:30.000000000 +0900
+++ include/linux/fb.h 2003-11-06 00:38:53.000000000 +0900
@@ -3,7 +3,6 @@
#include <linux/tty.h>
#include <asm/types.h>
-#include <asm/io.h>
/* Definitions of frame buffers */
@@ -335,6 +334,7 @@
#include <linux/fs.h>
#include <linux/init.h>
#include <linux/workqueue.h>
+#include <asm/io.h>
struct fb_info;
struct vm_area_struct;
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
prev parent reply other threads:[~2003-11-05 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 5:03 [PATCH] don't export fb.h internal structure to userland GOTO Masanori
2003-11-05 15:55 ` GOTO Masanori [this message]
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=80isly95em.wl@oris.opensource.jp \
--to=gotom@debian.or.jp \
--cc=dan@debian.org \
--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;
as well as URLs for NNTP newsgroup(s).