public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] quiet ide-cd warning
Date: Sat, 02 Apr 2005 03:46:53 +0400	[thread overview]
Message-ID: <424DDD6D.3010204@tls.msk.ru> (raw)
In-Reply-To: <20050401201111.GH15453@waste.org>

Matt Mackall wrote:
> This shuts up a potential uninitialized variable warning.

Potential warning or potential uninitialized use?
The code was right before the change, and if the compiler
generates such a warning on it, it's the compiler who
should be fixed, not the code: it's obvious the variable
can't be used uninitialized here, and moving the things
around like that makes the code misleading and hard to
understand...

/mjt

> Signed-off-by: Matt Mackall <mpm@selenic.com>
> 
> Index: af/drivers/ide/ide-cd.c
> ===================================================================
> --- af.orig/drivers/ide/ide-cd.c	2005-04-01 11:17:37.000000000 -0800
> +++ af/drivers/ide/ide-cd.c	2005-04-01 11:55:09.000000000 -0800
> @@ -430,7 +430,7 @@ void cdrom_analyze_sense_data(ide_drive_
>  #if VERBOSE_IDE_CD_ERRORS
>  	{
>  		int i;
> -		const char *s;
> +		const char *s = "bad sense key!";
>  		char buf[80];
>  
>  		printk ("ATAPI device %s:\n", drive->name);
> @@ -445,8 +445,6 @@ void cdrom_analyze_sense_data(ide_drive_
>  
>  		if (sense->sense_key < ARY_LEN(sense_key_texts))
>  			s = sense_key_texts[sense->sense_key];
> -		else
> -			s = "bad sense key!";
>  
>  		printk("%s -- (Sense key=0x%02x)\n", s, sense->sense_key);
>  
> 


  reply	other threads:[~2005-04-01 23:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01 20:11 [PATCH] quiet ide-cd warning Matt Mackall
2005-04-01 23:46 ` Michael Tokarev [this message]
2005-04-02  0:31   ` Matt Mackall

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=424DDD6D.3010204@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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