From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Potomski\, MichalX" <michalx.potomski@intel.com>
Cc: "'vinholikatti\@gmail.com'" <vinholikatti@gmail.com>,
"'subhashj\@codeaurora.org'" <subhashj@codeaurora.org>,
"'jejb\@linux.vnet.ibm.com'" <jejb@linux.vnet.ibm.com>,
"'martin.petersen\@oracle.com'" <martin.petersen@oracle.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>
Subject: Re: [PATCH v2] scsi: ufs: Factor out ufshcd_read_desc_param
Date: Mon, 27 Feb 2017 22:24:25 -0500 [thread overview]
Message-ID: <yq1k28bvvyu.fsf@oracle.com> (raw)
In-Reply-To: <C8BF859FC3044844854B2CBA1ED115C11B067E@HASMSX106.ger.corp.intel.com> (MichalX Potomski's message of "Thu, 23 Feb 2017 09:05:30 +0000")
>>>>> "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:?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-02-28 6:17 UTC|newest]
Thread overview: 4+ 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 [this message]
2017-03-01 18:29 ` Subhash Jadavani
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=yq1k28bvvyu.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=grzegorz.janca@intel.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michalx.potomski@intel.com \
--cc=subhashj@codeaurora.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).