From: Tom Rini <trini@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Paul Mackerras <paulus@samba.org>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: screen_info in 2.4.20-rc1
Date: Thu, 7 Nov 2002 11:37:40 -0700 [thread overview]
Message-ID: <20021107183739.GA6164@opus.bloom.county> (raw)
In-Reply-To: <Pine.GSO.4.21.0211071816370.3669-100000@vervain.sonytel.be>
On Thu, Nov 07, 2002 at 06:21:09PM +0100, Geert Uytterhoeven wrote:
> In 2.4.20-rc1, the declaration and export of screen_info[] depends on
> CONFIG_VGA_CONSOLE. However, it's also needed by vga16fb, which can be modular
> as well.
This is fixed in _devel (along with vesafb) and in 2.5. It was just
over looked for 2.4.20 I suppose. It's a low impact change, so I doubt
Paul would object to trying to get Marcelo to take it.
Paul?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-11-07 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 17:21 screen_info in 2.4.20-rc1 Geert Uytterhoeven
2002-11-07 18:37 ` Tom Rini [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=20021107183739.GA6164@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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