[Natty] UBUNTU: SAUCE: remove __initdata from vesafb_fix

BugLink: http://bugs.launchpad.net/bugs/969309

OK. Then, I think we also want to fix these warnings probably introduced by
commit a6021559 "UBUNTU: SAUCE: (no-up) Modularize vesafb".

WARNING: drivers/video/vesafb.o(.exit.text+0x42): Section mismatch in reference from the function vesafb_remove() to the (unknown reference) .init.data:(unknown)
The function __exit vesafb_remove() references
a (unknown reference) __initdata (unknown).
This is often seen when error handling in the exit function
uses functionality in the init path.
The fix is often to remove the __initdata annotation of
(unknown) so it may be used outside an init section.

WARNING: drivers/video/vesafb.o(.exit.text+0x4a): Section mismatch in reference from the function vesafb_remove() to the variable .init.data:vesafb_fix
The function __exit vesafb_remove() references
a variable __initdata vesafb_fix.
This is often seen when error handling in the exit function
uses functionality in the init path.
The fix is often to remove the __initdata annotation of
vesafb_fix so it may be used outside an init section.

Reported-by: Tetsuo Honda <from-ubuntu@I-love.SAKURA.ne.jp>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
---
 drivers/video/vesafb.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

On 30.03.2012 17:51, Tim Gardner wrote:
> BugLink: http://bugs.launchpad.net/bugs/969309
> 
> OK. Then, I think we also want to fix these warnings probably introduced by
> commit a6021559 "UBUNTU: SAUCE: (no-up) Modularize vesafb".
> 
> WARNING: drivers/video/vesafb.o(.exit.text+0x42): Section mismatch in reference from the function vesafb_remove() to the (unknown reference) .init.data:(unknown)
> The function __exit vesafb_remove() references
> a (unknown reference) __initdata (unknown).
> This is often seen when error handling in the exit function
> uses functionality in the init path.
> The fix is often to remove the __initdata annotation of
> (unknown) so it may be used outside an init section.
> 
> WARNING: drivers/video/vesafb.o(.exit.text+0x4a): Section mismatch in reference from the function vesafb_remove() to the variable .init.data:vesafb_fix
> The function __exit vesafb_remove() references
> a variable __initdata vesafb_fix.
> This is often seen when error handling in the exit function
> uses functionality in the init path.
> The fix is often to remove the __initdata annotation of
> vesafb_fix so it may be used outside an init section.
> 
> Reported-by: Tetsuo Honda <from-ubuntu@I-love.SAKURA.ne.jp>
> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
> ---
>  drivers/video/vesafb.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/video/vesafb.c b/drivers/video/vesafb.c
> index b98a211..c71f23c 100644
> --- a/drivers/video/vesafb.c
> +++ b/drivers/video/vesafb.c
> @@ -46,7 +46,7 @@ static struct fb_var_screeninfo vesafb_defined __initdata = {
>  	.vmode		= FB_VMODE_NONINTERLACED,
>  };
>  
> -static struct fb_fix_screeninfo vesafb_fix __initdata = {
> +static struct fb_fix_screeninfo vesafb_fix = {
>  	.id	= "VESA VGA",
>  	.type	= FB_TYPE_PACKED_PIXELS,
>  	.accel	= FB_ACCEL_NONE,

On 30/03/12 16:51, Tim Gardner wrote:
> BugLink: http://bugs.launchpad.net/bugs/969309
>
> OK. Then, I think we also want to fix these warnings probably introduced by
> commit a6021559 "UBUNTU: SAUCE: (no-up) Modularize vesafb".
>
> WARNING: drivers/video/vesafb.o(.exit.text+0x42): Section mismatch in reference from the function vesafb_remove() to the (unknown reference) .init.data:(unknown)
> The function __exit vesafb_remove() references
> a (unknown reference) __initdata (unknown).
> This is often seen when error handling in the exit function
> uses functionality in the init path.
> The fix is often to remove the __initdata annotation of
> (unknown) so it may be used outside an init section.
>
> WARNING: drivers/video/vesafb.o(.exit.text+0x4a): Section mismatch in reference from the function vesafb_remove() to the variable .init.data:vesafb_fix
> The function __exit vesafb_remove() references
> a variable __initdata vesafb_fix.
> This is often seen when error handling in the exit function
> uses functionality in the init path.
> The fix is often to remove the __initdata annotation of
> vesafb_fix so it may be used outside an init section.
>
> Reported-by: Tetsuo Honda<from-ubuntu@I-love.SAKURA.ne.jp>
> Signed-off-by: Tim Gardner<tim.gardner@canonical.com>
> ---
>   drivers/video/vesafb.c |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/video/vesafb.c b/drivers/video/vesafb.c
> index b98a211..c71f23c 100644
> --- a/drivers/video/vesafb.c
> +++ b/drivers/video/vesafb.c
> @@ -46,7 +46,7 @@ static struct fb_var_screeninfo vesafb_defined __initdata = {
>   	.vmode		= FB_VMODE_NONINTERLACED,
>   };
>
> -static struct fb_fix_screeninfo vesafb_fix __initdata = {
> +static struct fb_fix_screeninfo vesafb_fix = {
>   	.id	= "VESA VGA",
>   	.type	= FB_TYPE_PACKED_PIXELS,
>   	.accel	= FB_ACCEL_NONE,

Applied to Natty.

-apw