linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Buttchereit, Axel (XL)" <XL@XLsigned.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [patch] allow fb_find_mode() w/ default db from modules
Date: Thu, 10 Feb 2005 17:37:14 +0100	[thread overview]
Message-ID: <420B8DBA.50105@XLsigned.net> (raw)
In-Reply-To: <420B8AEE.5090500@arcom.com>

Is there any reason why this has been originally flagged "__init"?
"vesa_modes" is not "__init". That's why I changed "intelfb" to
use "vesa_modes".

--Axel   

David Vrabel wrote:
> Remove the __init from modedb in modedb.c so it can be used from modules
> as the default db in fb_find_mode().
> 
> Signed-off-by: David Vrabel
> 
> Index: linux-2.6-i386/drivers/video/modedb.c
> ===================================================================
> --- linux-2.6-i386.orig/drivers/video/modedb.c	2005-02-10
> 15:54:58.682358203 +0000
> +++ linux-2.6-i386/drivers/video/modedb.c	2005-02-10 15:57:29.956725460
> +0000
> @@ -39,7 +39,7 @@
> 
>  #define DEFAULT_MODEDB_INDEX	0
> 
> -static const __init struct fb_videomode modedb[] = {
> +static const struct fb_videomode modedb[] = {
>      {
>  	/* 640x400 @ 70 Hz, 31.5 kHz hsync */
>  	NULL, 70, 640, 400, 39721, 40, 24, 39, 9, 96, 2,


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

      reply	other threads:[~2005-02-10 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 16:25 [patch] allow fb_find_mode() w/ default db from modules David Vrabel
2005-02-10 16:37 ` Buttchereit, Axel (XL) [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=420B8DBA.50105@XLsigned.net \
    --to=xl@xlsigned.net \
    --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).