[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3c5dde7cd24cf10707b682cce0cac74e5ac37e9b.camel@gmail.com>
Date: Fri, 30 Apr 2021 10:47:46 +0200
From: Bean Huo <huobean@...il.com>
To: keosung.park@...sung.com, ALIM AKHTAR <alim.akhtar@...sung.com>,
"avri.altman@....com" <avri.altman@....com>,
"jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"stanley.chu@...iatek.com" <stanley.chu@...iatek.com>,
"cang@...eaurora.org" <cang@...eaurora.org>,
"beanhuo@...ron.com" <beanhuo@...ron.com>,
"jaegeuk@...nel.org" <jaegeuk@...nel.org>,
"adrian.hunter@...el.com" <adrian.hunter@...el.com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: Daejun Park <daejun7.park@...sung.com>,
Sung-Jun Park <sungjun07.park@...sung.com>,
Jinyoung CHOI <j-young.choi@...sung.com>
Subject: Re: [PATCH] scsi: ufs: remove redundant initialization of variable
On Fri, 2021-04-30 at 11:14 +0900, Keoseong Park wrote:
> The variable d_lu_wb_buf_alloc may be repeatedly initialized to 0 in
> a for-loop.
>
> If the variable is set to a value other than 0, it exits the for-
> loop, so there is no need to reset it to 0.
>
>
>
> Since lun and d_lu_wb_buf_alloc are just being used in a else
> statement inside a local scope, move the declaration of the variables
> to that scope.
>
>
>
> Signed-off-by: Keoseong Park <keosung.park@...sung.com>
UFS Spec 3.1, bDeviceMaxWriteBoosterLUs is 01h, for LU dedicated buffer
mode, WriteBooster Buffer can be configured in only one logical unit.
Bean
Powered by blists - more mailing lists