linux-kernel - Re: [PATCH] lpfc: two branches the same in lpfc_decode_firmware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4B563502.6070908@emulex.com>
Date:	Tue, 19 Jan 2010 17:41:06 -0500
From:	James Smart <james.smart@...lex.com>
To:	Roel Kluin <roel.kluin@...il.com>
CC:	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] lpfc: two branches the same in lpfc_decode_firmware_rev()

Acked-by:  James Smart <james.smart@...lex.com>

-- james s



Roel Kluin wrote:
> Regardless of the flag state, the branches execute the same code
> 
> Signed-off-by: Roel Kluin <roel.kluin@...il.com>
> ---
>  drivers/scsi/lpfc/lpfc_ct.c |    7 +------
>  1 files changed, 1 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/scsi/lpfc/lpfc_ct.c b/drivers/scsi/lpfc/lpfc_ct.c
> index 0ebcd9b..bf7bf62 100644
> --- a/drivers/scsi/lpfc/lpfc_ct.c
> +++ b/drivers/scsi/lpfc/lpfc_ct.c
> @@ -1843,12 +1843,7 @@ lpfc_decode_firmware_rev(struct lpfc_hba *phba, char *fwrevision, int flag)
>  		c  = (rev & 0x0000ff00) >> 8;
>  		b4 = (rev & 0x000000ff);
>  
> -		if (flag)
> -			sprintf(fwrevision, "%d.%d%d%c%d ", b1,
> -				b2, b3, c, b4);
> -		else
> -			sprintf(fwrevision, "%d.%d%d%c%d ", b1,
> -				b2, b3, c, b4);
> +		sprintf(fwrevision, "%d.%d%d%c%d", b1, b2, b3, c, b4);
>  	}
>  	return;
>  }
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/