From: Subhash Jadavani <subhashj@codeaurora.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: "Potomski, MichalX" <michalx.potomski@intel.com>,
"'vinholikatti@gmail.com'" <vinholikatti@gmail.com>,
"'jejb@linux.vnet.ibm.com'" <jejb@linux.vnet.ibm.com>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"Janca, Grzegorz" <grzegorz.janca@intel.com>,
"Mielczarek, SzymonX" <szymonx.mielczarek@intel.com>,
linux-scsi-owner@vger.kernel.org
Subject: Re: [PATCH v2] scsi: ufs: Factor out ufshcd_read_desc_param
Date: Wed, 01 Mar 2017 10:29:13 -0800 [thread overview]
Message-ID: <b3b74939fba413113eef30865bc6f2ba@codeaurora.org> (raw)
In-Reply-To: <yq1k28bvvyu.fsf@oracle.com>
On 2017-02-27 19:24, Martin K. Petersen wrote:
>>>>>> "Michal" == Potomski, MichalX <michalx.potomski@intel.com> writes:
>
> Michal> Since in UFS 2.1 specification some of the descriptor lengths
> Michal> differs from 2.0 specification and some devices, which are
> Michal> reporting spec version 2.0 have different descriptor lengths we
> Michal> can not rely on hardcoded values taken from 2.0
> Michal> specification. This patch introduces reading these lengths per
> Michal> each device from descriptor headers at probe time to ensure
> Michal> their correctness.
>
> Subhash: I assume v2 still carries your Reviewed-by:?
Yes, v2 also looks good to me.
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-03-01 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 9:05 [PATCH v2] scsi: ufs: Factor out ufshcd_read_desc_param Potomski, MichalX
2017-02-28 3:24 ` Martin K. Petersen
2017-02-28 3:24 ` Martin K. Petersen
2017-03-01 18:29 ` Subhash Jadavani [this message]
2017-03-02 2:44 ` Martin K. Petersen
2017-03-02 2:44 ` Martin K. Petersen
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=b3b74939fba413113eef30865bc6f2ba@codeaurora.org \
--to=subhashj@codeaurora.org \
--cc=grzegorz.janca@intel.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michalx.potomski@intel.com \
--cc=szymonx.mielczarek@intel.com \
--cc=vinholikatti@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.