From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [RFC: 2.6 patch] i386: EXPORT_SYMBOL(screen_info) even #ifndef CONFIG_VT
Date: Wed, 02 Nov 2005 08:43:44 +0800 [thread overview]
Message-ID: <43680BC0.70805@pol.net> (raw)
In-Reply-To: <20051101152207.GT8009@stusta.de>
Adrian Bunk wrote:
> The folllowing modules require screen_info but don't depend
> on CONFIG_VT:
> - vga16fb.ko
> - intelfb.ko
>
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Ok with me.
Tony
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
WARNING: multiple messages have this Message-ID (diff)
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [RFC: 2.6 patch] i386: EXPORT_SYMBOL(screen_info) even #ifndef CONFIG_VT
Date: Wed, 02 Nov 2005 08:43:44 +0800 [thread overview]
Message-ID: <43680BC0.70805@pol.net> (raw)
In-Reply-To: <20051101152207.GT8009@stusta.de>
Adrian Bunk wrote:
> The folllowing modules require screen_info but don't depend
> on CONFIG_VT:
> - vga16fb.ko
> - intelfb.ko
>
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Ok with me.
Tony
next prev parent reply other threads:[~2005-11-02 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 15:22 [RFC: 2.6 patch] i386: EXPORT_SYMBOL(screen_info) even #ifndef CONFIG_VT Adrian Bunk
2005-11-02 0:43 ` Antonino A. Daplas [this message]
2005-11-02 0:43 ` Antonino A. Daplas
-- strict thread matches above, loose matches on Subject: below --
2005-11-07 21:19 Adrian Bunk
2005-11-07 21:19 ` Adrian Bunk
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=43680BC0.70805@pol.net \
--to=adaplas@gmail.com \
--cc=bunk@stusta.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.