linux-kernel - Re: [PATCH v1 1/2] scsi: ufs-qcom: save controller revision info in internal structure

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 7 Apr 2015 07:39:31 -0000
From:	"Gilad Broner" <gbroner@...eaurora.org>
To:	"Yaniv Gardi" <ygardi@...eaurora.org>
Cc:	james.bottomley@...senpartnership.com, hch@...radead.org,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	linux-arm-msm@...r.kernel.org, santoshsy@...il.com,
	linux-scsi-owner@...r.kernel.org, ygardi@...eaurora.org,
	"Vinayak Holikatti" <vinholikatti@...il.com>,
	"James E.J. Bottomley" <jbottomley@...allels.com>
Subject: Re: [PATCH v1 1/2] scsi: ufs-qcom: save controller revision info in
 internal structure


> Sometimes, specific information about the UFS controller revision is
> required in order to determine certain operations or execute
> controller dependent quirks.
> In order to avoid reading the controller revision multiple times,
> we simply read it once and save this information in internal structure.
>
> Signed-off-by: Yaniv Gardi <ygardi@...eaurora.org>
>
> ---
>  drivers/scsi/ufs/ufs-qcom.c | 14 +++++++-------
>  drivers/scsi/ufs/ufs-qcom.h |  8 ++++++++
>  2 files changed, 15 insertions(+), 7 deletions(-)
>

Reviewed-by: Gilad Broner <gbroner@...eaurora.org>


-- 
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

--
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/