From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: spock@gentoo.org, linux-fbdev-devel@lists.sourceforge.net,
akpm <akpm@linux-foundation.org>,
adaplas@gmail.com
Subject: Re: [PATCH] uvesafb: fix section mismatch warnings
Date: Sat, 12 Jan 2008 11:42:03 +0100 [thread overview]
Message-ID: <20080112104203.GC2523@uranus.ravnborg.org> (raw)
In-Reply-To: <20080111170409.10ecb8a9.rdunlap@xenotime.net>
On Fri, Jan 11, 2008 at 05:04:09PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Mark uvesafb_init_mtrr() as __devinit since its caller is __devinit
> and since it accesses __devinitdata.
>
> WARNING: vmlinux.o(.text+0x4df80e): Section mismatch: reference to .init.data: (between 'uvesafb_init_mtrr' and 'uvesafb_show_vbe_ver')
OK
>
> Variable 'blank' cannot be __devinitdata since it is referenced in an
> fb_ops method that could be called at any time.
The patch is correct but the explanation is wrong.
uvesafb uses local variables named blank in two spots that hides the
global defined blank which I assume has confused you.
The problematic spot is this use as a parameter:
module_param(blank, bool, 0);
MODULE_PARM_DESC(blank, "Enable hardware blanking");
This is at least how I understand it looking at the code.
Sam
>
> WARNING: vmlinux.o(.text+0x4dfc1e): Section mismatch: reference to .init.data:blank (between 'param_set_scroll' and 'vesa_setpalette')
> WARNING: vmlinux.o(.text+0x4dfc24): Section mismatch: reference to .init.data:blank (between 'param_set_scroll' and 'vesa_setpalette')
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
> drivers/video/uvesafb.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-2.6.24-rc7-git1.orig/drivers/video/uvesafb.c
> +++ linux-2.6.24-rc7-git1/drivers/video/uvesafb.c
> @@ -43,7 +43,7 @@ static struct fb_fix_screeninfo uvesafb_
> };
>
> static int mtrr __devinitdata = 3; /* enable mtrr by default */
> -static int blank __devinitdata = 1; /* enable blanking by default */
> +static int blank = 1; /* enable blanking by default */
> static int ypan __devinitdata = 1; /* 0: scroll, 1: ypan, 2: ywrap */
> static int pmi_setpal __devinitdata = 1; /* use PMI for palette changes */
> static int nocrtc __devinitdata; /* ignore CRTC settings */
> @@ -1549,7 +1549,7 @@ static void __devinit uvesafb_init_info(
> info->fbops->fb_pan_display = NULL;
> }
>
> -static void uvesafb_init_mtrr(struct fb_info *info)
> +static void __devinit uvesafb_init_mtrr(struct fb_info *info)
> {
> #ifdef CONFIG_MTRR
> if (mtrr && !(info->fix.smem_start & (PAGE_SIZE - 1))) {
> ---
> ~Randy
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next prev parent reply other threads:[~2008-01-12 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 1:04 [PATCH] uvesafb: fix section mismatch warnings Randy Dunlap
2008-01-12 10:42 ` Sam Ravnborg [this message]
2008-01-13 18:31 ` Randy Dunlap
2008-01-14 13:53 ` Sam Ravnborg
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=20080112104203.GC2523@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=rdunlap@xenotime.net \
--cc=spock@gentoo.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).