public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andreas Schwab <schwab@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/cdrom/gscd.c: kill dead code
Date: Thu, 24 Mar 2005 00:54:20 +0100	[thread overview]
Message-ID: <20050323235420.GH1948@stusta.de> (raw)
In-Reply-To: <jemzsvb8oz.fsf@sykes.suse.de>

On Tue, Mar 22, 2005 at 11:46:20PM +0100, Andreas Schwab wrote:
> Adrian Bunk <bunk@stusta.de> writes:
> 
> > This patch removes some obviously dead code found by the Coverity 
> > checker.
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> > --- linux-2.6.12-rc1-mm1-full/drivers/cdrom/gscd.c.old	2005-03-22 20:58:54.000000000 +0100
> > +++ linux-2.6.12-rc1-mm1-full/drivers/cdrom/gscd.c	2005-03-22 20:59:46.000000000 +0100
> > @@ -694,12 +694,8 @@
> >  		do {
> >  			result = wait_drv_ready();
> >  		} while (result != 6 || result == 0x0E);
> >  
> > -		if (result != 6) {
> > -			cmd_end();
> > -			return;
> > -		}
> 
> I'd rather guess that (result != 6 || result == 0x0E) is borken, since
> it's equivalent to (result != 6).

This driver seems to be pretty unchanged for the last 10 years.

Unless someone really knows your assumption was correct, I'd prefer 
staying with the old behavior.

> Andreas.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



      reply	other threads:[~2005-03-23 23:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-22 21:55 [2.6 patch] drivers/cdrom/gscd.c: kill dead code Adrian Bunk
2005-03-22 22:46 ` Andreas Schwab
2005-03-23 23:54   ` Adrian Bunk [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=20050323235420.GH1948@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwab@suse.de \
    /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