public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: SCSI development list <linux-scsi@vger.kernel.org>,
	Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	"Martin K. Petersen" <martin.petersen@ORACLE.COM>
Subject: [PATCH v2 0/5] scsi_debug: switch to table based parser
Date: Mon, 24 Nov 2014 23:04:09 -0500	[thread overview]
Message-ID: <5473FFB9.8070206@interlog.com> (raw)

This series of patches is in response to Hannes' comments
earlier today. He wanted the single large patch broken up.

Changes since v1:
    - break single big patch into 4 smaller ones and one less
      large
    - resync with drivers-for-3.19

Patches:
     [PATCH v2 1/5] pinpoint invalid field in sense data
     [PATCH v2 2/5] append inject error flags onto scsi_cmnd object
     [PATCH v2 3/5] add Capacity Changed Unit Attention
     [PATCH v2 4/5] change SCSI command parser to table driven
     [PATCH v2 5/5] Add Report supported opcodes+tmfs; Compare and write

Todo:
    - re-order teardown in scsi_debug_exit()
    - make sdebug_dev_info::stopped atomic (add to end of uas_bm ?)
    - review Rob Elliott's suggestions; look at speed ups
    - remove host_lock logic and make the host_lock option a dummy
    - update some mode page and VPD data to reflect more recent
      devices
    - changing remaining >> and << byte handling over to
      get/put_unaligned_be*()
    - set INFO field for COMPARE AND WRITE command MISCOMPAREs


Hannes also asked that XDWRITEREAD_10 be added to scsi.h . It has
been there for a while. I guess he meant something else.


Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>

             reply	other threads:[~2014-11-25  4:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25  4:04 Douglas Gilbert [this message]
2014-11-25 14:45 ` [PATCH v2 0/5] scsi_debug: switch to table based parser 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=5473FFB9.8070206@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@ORACLE.COM \
    /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