From: Meelis Roos <mroos@linux.ee>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
David Miller <davem@davemloft.net>,
linux-scsi@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: fix blk-mq for SPI hosts
Date: Thu, 23 Oct 2014 13:49:07 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.11.1410231151160.2821@adalberg.ut.ee> (raw)
In-Reply-To: <20141023084530.GB20233@infradead.org>
> ping?
Sorry, forgot to reply. Yes, it worked fine, on the initial Ultra 1 and
additionally on Ultra 2 too.
> On Sun, Oct 19, 2014 at 05:13:56PM +0200, Christoph Hellwig wrote:
> > Fix the assumption that we can treat all blk-mq requests as tagged. For
> > traditional SCSI that's wrong, as being tagged has a very explicit meaning
> > on the wire.
> >
> > This is a little bit different from the version Meelis tested earlier, but
> > the concept is the same. I didn't want to add a Tested-by tag as it's
> > different enough, though.
> >
> > --
> > 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
> ---end quoted text---
>
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2014-10-23 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 15:13 fix blk-mq for SPI hosts Christoph Hellwig
2014-10-19 15:13 ` [PATCH 1/2] Revert "block: all blk-mq requests are tagged" Christoph Hellwig
2014-10-28 0:23 ` Martin K. Petersen
2014-10-19 15:13 ` [PATCH 2/2] scsi: set REQ_QUEUE for the blk-mq case Christoph Hellwig
2014-10-28 0:24 ` Martin K. Petersen
2014-10-23 8:45 ` fix blk-mq for SPI hosts Christoph Hellwig
2014-10-23 10:49 ` Meelis Roos [this message]
2014-10-23 17:14 ` Christoph Hellwig
2014-10-23 17:16 ` Jens Axboe
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=alpine.LRH.2.11.1410231151160.2821@adalberg.ut.ee \
--to=mroos@linux.ee \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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).