From: "Dolev Raviv" <draviv@codeaurora.org>
To: James.Bottomley@HansenPartnership.com
Cc: linux-scsi@vger.kernel.org, linux-scsi-owner@vger.kernel.org,
sthumma@codeaurora.org, linux-arm-msm@vger.kernel.org
Subject: RE: [PATCH V1 0/4] scsi: ufs: LU queue depth managment
Date: Tue, 27 May 2014 11:46:58 +0300 [thread overview]
Message-ID: <002c01cf7988$3ab24af0$b016e0d0$@codeaurora.org> (raw)
Fixing a typo in the Subject.
Thanks,
Dolev
--
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
-----Original Message-----
From: linux-scsi-owner@vger.kernel.org
[mailto:linux-scsi-owner@vger.kernel.org] On Behalf Of Dolev Raviv
Sent: Tuesday, May 27, 2014 10:22 AM
To: James.Bottomley@HansenPartnership.com
Cc: linux-scsi@vger.kernel.org; linux-scsi-owner@vger.kernel.org;
sthumma@codeaurora.org; linux-arm-msm@vger.kernel.org; Dolev Raviv
Subject: [PATCH V1 0/4] LU queue depth manament
Some UFS devices don't support a LUN queue depth same as the device queue
depth. This requires reading the unit descriptor for extracting the LU's
queue depth.
Dolev Raviv (1):
scsi: ufs: query descriptor API
Raviv Shvili (2):
scsi: ufs: device query status and size check
scsi: ufs: Logical Unit (LU) command queue depth
Sujit Reddy Thumma (1):
scsi: ufs: Fix queue depth handling for best effort cases
drivers/scsi/ufs/ufs.h | 38 +++++-
drivers/scsi/ufs/ufshcd.c | 318
++++++++++++++++++++++++++++++++--------------
2 files changed, 261 insertions(+), 95 deletions(-)
--
1.8.5.2
--
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the
body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
reply other threads:[~2014-05-27 8:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='002c01cf7988$3ab24af0$b016e0d0$@codeaurora.org' \
--to=draviv@codeaurora.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sthumma@codeaurora.org \
/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).