All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dolev Raviv <draviv@codeaurora.org>
Cc: James.Bottomley@HansenPartnership.com,
	linux-scsi@vger.kernel.org, linux-scsi-owner@vger.kernel.org,
	sthumma@codeaurora.org, linux-arm-msm@vger.kernel.org,
	santoshsy@gmail.com
Subject: Re: [PATCH V2 0/5] scsi: ufs: LU queue depth management
Date: Tue, 22 Jul 2014 09:05:33 -0700	[thread overview]
Message-ID: <20140722160533.GA3345@infradead.org> (raw)
In-Reply-To: <1406039030-14246-1-git-send-email-draviv@codeaurora.org>

On Tue, Jul 22, 2014 at 05:23:45PM +0300, Dolev Raviv wrote:
> 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.

Can you please send just the sparse fixes against the tree at:

	http://git.infradead.org/users/hch/scsi-queue.git/shortlog/refs/heads/drivers-for-3.17

which already has the previous version merged?  

      parent reply	other threads:[~2014-07-22 16:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 14:23 [PATCH V2 0/5] scsi: ufs: LU queue depth management Dolev Raviv
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 ` Christoph Hellwig [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=20140722160533.GA3345@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=draviv@codeaurora.org \
    --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 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.