public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	Bill Pemberton <wfp5p@virginia.edu>,
	Arnaud Patard <apatard@mandriva.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] staging: xgifb: Initialize uninitialized variables
Date: Tue, 07 Sep 2010 10:46:27 +0200	[thread overview]
Message-ID: <4C85FBE3.4000605@gmail.com> (raw)
In-Reply-To: <1283837645.6302.10.camel@lenovo>

On 09/07/2010 07:34 AM, Javier Martinez Canillas wrote:
> Current patch solves compilation warnings in staging/xgifb for using possibly uninitialized variables.
> 
> Signed-off-by: Javier Martinez Canillas <martinez.javier@gmail.com>
> ---
>  drivers/staging/xgifb/vb_setmode.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/xgifb/vb_setmode.c b/drivers/staging/xgifb/vb_setmode.c
> index c4db2fc..720a592 100644
> --- a/drivers/staging/xgifb/vb_setmode.c
> +++ b/drivers/staging/xgifb/vb_setmode.c
> @@ -376,7 +376,7 @@ void InitTo330Pointer(unsigned char ChipType, struct vb_device_info *pVBInfo)
>  unsigned char XGISetModeNew(struct xgi_hw_device_info *HwDeviceExtension,
>  			unsigned short ModeNo)
>  {
> -	unsigned short ModeIdIndex;
> +	unsigned short ModeIdIndex = 0;
>  	/* unsigned char *pVBInfo->FBAddr = HwDeviceExtension->pjVideoMemoryAddress; */
>  	struct vb_device_info VBINF;
>  	struct vb_device_info *pVBInfo = &VBINF;

No, please don't. This is a compiler bug.

The first use in that function is:
XGI_SearchModeID( ModeNo , &ModeIdIndex, pVBInfo );

and that function contains:
if (XYZ) {
  for( *ModeIdIndex = 0 ; ; ( *ModeIdIndex )++ )
    ...
} else {
  for( *ModeIdIndex = 0 ; ; ( *ModeIdIndex )++ )
    ...
}

So your compiler is foolish if that emits a warning.

> @@ -3834,7 +3834,7 @@ unsigned char XGI_SetCRT2Group301(unsigned short ModeNo,
>  		struct xgi_hw_device_info *HwDeviceExtension,
>  		struct vb_device_info *pVBInfo)
>  {
> -	unsigned short tempbx, ModeIdIndex, RefreshRateTableIndex;
> +	unsigned short tempbx, ModeIdIndex = 0, RefreshRateTableIndex;
>  
>  	tempbx = pVBInfo->VBInfo;
>  	pVBInfo->SetFlag |= ProgrammingCRT2;

The same here.

regards,
-- 
js

  reply	other threads:[~2010-09-07  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07  5:34 [PATCH 3/3] staging: xgifb: Initialize uninitialized variables Javier Martinez Canillas
2010-09-07  8:46 ` Jiri Slaby [this message]
2010-09-08  0:38   ` Greg KH
2010-09-08  7:16     ` Jiri Slaby
2010-09-08  8:49       ` Greg KH

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=4C85FBE3.4000605@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=apatard@mandriva.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martinez.javier@gmail.com \
    --cc=randy.dunlap@oracle.com \
    --cc=wfp5p@virginia.edu \
    /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