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] scsi: ufs: Factor out ufshcd_read_desc_param
Date: Wed, 22 Feb 2017 19:25:53 -0500 [thread overview]
Message-ID: <yq160k192i6.fsf@oracle.com> (raw)
In-Reply-To: <C8BF859FC3044844854B2CBA1ED115C11B053C@HASMSX106.ger.corp.intel.com> (MichalX Potomski's message of "Tue, 21 Feb 2017 07:36:16 +0000")
>>>>> "Michal" == Potomski, MichalX <michalx.potomski@intel.com> writes:
Michal,
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.
This doesn't apply to 4.11/scsi-fixes. Please rebase and resend.
Thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-02-23 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C8BF859FC3044844854B2CBA1ED115C11B0163@HASMSX106.ger.corp.intel.com>
2017-02-21 7:36 ` [PATCH] scsi: ufs: Factor out ufshcd_read_desc_param Potomski, MichalX
2017-02-22 23:23 ` Subhash Jadavani
2017-02-23 0:25 ` Martin K. Petersen [this message]
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=yq160k192i6.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