[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <X/whZfoRQvEncfUS@google.com>
Date: Mon, 11 Jan 2021 01:59:01 -0800
From: Jaegeuk Kim <jaegeuk@...nel.org>
To: Avri Altman <Avri.Altman@....com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"kernel-team@...roid.com" <kernel-team@...roid.com>,
"cang@...eaurora.org" <cang@...eaurora.org>,
"alim.akhtar@...sung.com" <alim.akhtar@...sung.com>,
"bvanassche@....org" <bvanassche@....org>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"stanley.chu@...iatek.com" <stanley.chu@...iatek.com>
Subject: Re: [PATCH v2] scsi: ufs: WB is not allowed in RPMB_LUN
On 01/11, Avri Altman wrote:
> > static inline bool ufs_is_valid_unit_desc_lun(struct ufs_dev_info *dev_info,
> > - u8 lun)
> > + u8 lun, u8 param_offset)
> > {
> > if (!dev_info || !dev_info->max_lu_supported) {
> > pr_err("Max General LU supported by UFS isn't initialized\n");
> > return false;
> > }
> > -
> > + /* WB is not allowed in RPMB_WLUN */
> /* wb is only allowed to either a sha*/
> > + if (param_offset == UNIT_DESC_PARAM_WB_BUF_ALLOC_UNITS)
> > + return lun < dev_info->max_lu_supported;
> I think here you should use UFS_UPIU_MAX_WB_LUN_ID and not dev_info->max_lu_supported.
Ok, sending v3.
>
> Thanks,
> Avri
Powered by blists - more mailing lists