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,
santoshsy@gmail.com, Dolev Raviv <draviv@codeaurora.org>
Subject: [PATCH V2 0/5] scsi: ufs: LU queue depth management
Date: Tue, 22 Jul 2014 17:23:45 +0300 [thread overview]
Message-ID: <1406039030-14246-1-git-send-email-draviv@codeaurora.org> (raw)
New version to fix multiple 'sparse' warnings.
Add a driver wide fix to the endian 'sparse' warnings.
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.
Changes from V1:
- Add static modifier to ufshcd_query_descriptor function due to 'sparse'
warrning in [PATCH V1 1/4]
- Add new patch [PATCH V2 2/5] to deal with 'sparse' endian warnings
- Fix buf_len endian on [PATCH V1 2/4]
Dolev Raviv (1):
scsi: ufs: device query status and size check
scsi: ufs: query descriptor API
scsi: ufs: Logical Unit (LU) command queue depth
Sujit Reddy Thumma (2):
scsi: ufs: fix endianness sparse warnings
scsi: ufs: Fix queue depth handling for best effort cases
drivers/scsi/ufs/ufs.h | 38 +++++-
drivers/scsi/ufs/ufshcd.c | 319 ++++++++++++++++++++++++++++++++--------------
2 files changed, 262 insertions(+), 95 deletions(-)
--
1.8.5.2
next reply other threads:[~2014-07-22 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 14:23 Dolev Raviv [this message]
2014-07-22 14:23 ` [PATCH 1/5] scsi: ufs: query descriptor API Dolev Raviv
2014-07-22 14:23 ` [PATCH V2 2/5] scsi: ufs: fix endianness sparse warnings Dolev Raviv
2014-07-22 14:23 ` [PATCH V2 3/5] scsi: ufs: device query status and size check Dolev Raviv
2014-07-22 14:23 ` [PATCH V2 4/5] scsi: ufs: Logical Unit (LU) command queue depth Dolev Raviv
2014-07-22 14:23 ` [PATCH V2 5/5] scsi: ufs: Fix queue depth handling for best effort cases Dolev Raviv
2014-07-22 16:05 ` [PATCH V2 0/5] scsi: ufs: LU queue depth management Christoph Hellwig
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=1406039030-14246-1-git-send-email-draviv@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=santoshsy@gmail.com \
--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).