virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@fb.com>, mst@redhat.com, jasowang@redhat.com
Cc: linux-block@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: make SCSI passthrough support optional
Date: Sat, 28 Jan 2017 09:32:48 +0100	[thread overview]
Message-ID: <1485592373-29837-1-git-send-email-hch@lst.de> (raw)

Hi all,

this series builds on my previous changes in Jens' for-4.11/rq-refactor
branch that split out the BLOCK_PC fields from struct request into a new
struct scsi_request, and makes support for struct scsi_request and the
SCSI passthrough ioctls optional.  It is now only enabled by drivers that
need it.

In addition I've made SCSI passthrough support in the virtio_blk driver an
optional compile time feature, as it's not actually needed for most
common setups.

             reply	other threads:[~2017-01-28  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28  8:32 Christoph Hellwig [this message]
2017-01-28  8:32 ` [PATCH 1/5] nvme/scsi: don't rely on BLK_MAX_CDB Christoph Hellwig
2017-01-28  8:32 ` [PATCH 2/5] skd: implement trivial scsi ioctls directly Christoph Hellwig
2017-01-28  8:32 ` [PATCH 3/5] block: make scsi_request and scsi ioctl support optional Christoph Hellwig
2017-01-28  8:32 ` [PATCH 4/5] virtio_blk: remove struct request backpointer from virtblk_req Christoph Hellwig
2017-01-28  8:32 ` [PATCH 5/5] virtio_blk: make SCSI passthrough support configurable Christoph Hellwig
2017-01-31 17:56 ` make SCSI passthrough support optional 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=1485592373-29837-1-git-send-email-hch@lst.de \
    --to=hch@lst.de \
    --cc=axboe@fb.com \
    --cc=jasowang@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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).