From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: James Bottomley <jbottomley@odin.com>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Hannes Reinecke <hare@suse.de>,
Mike Christie <michaelc@cs.wisc.edu>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>,
Andrzej Pietrasiewicz <andrzej.p@samsung.com>
Subject: Re: [PATCH v4 3/5] Replace MAX_COMMAND_SIZE with BLK_MAX_CDB
Date: Mon, 11 May 2015 09:56:44 +0200 [thread overview]
Message-ID: <20150511075644.GA32395@lst.de> (raw)
In-Reply-To: <5550605B.904@sandisk.com>
On Mon, May 11, 2015 at 09:55:07AM +0200, Bart Van Assche wrote:
> Actually this makes my job easier because it allows me to drop a whole
> bunch of changes. Is the patch below what you had in mind ?
Yes, this looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2015-05-11 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 8:06 [PATCH v4 0/5] Split SCSI header files Bart Van Assche
2015-05-08 8:07 ` [PATCH v4 1/5] " Bart Van Assche
2015-05-08 12:36 ` Hannes Reinecke
2015-05-11 6:31 ` Christoph Hellwig
2015-05-08 8:07 ` [PATCH v4 2/5] Move code that is used both by initiator and target drivers Bart Van Assche
2015-05-08 12:37 ` Hannes Reinecke
2015-05-11 6:31 ` Christoph Hellwig
2015-05-08 8:08 ` [PATCH v4 3/5] Replace MAX_COMMAND_SIZE with BLK_MAX_CDB Bart Van Assche
2015-05-08 12:37 ` Hannes Reinecke
2015-05-11 6:32 ` Christoph Hellwig
2015-05-11 7:55 ` Bart Van Assche
2015-05-11 7:56 ` Christoph Hellwig [this message]
2015-05-08 8:08 ` [PATCH v4 4/5] target: Correct a comment Bart Van Assche
2015-05-08 12:38 ` Hannes Reinecke
2015-05-08 8:11 ` [PATCH v4 5/5] target: Minimize SCSI header #include directives Bart Van Assche
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=20150511075644.GA32395@lst.de \
--to=hch@lst.de \
--cc=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=bart.vanassche@sandisk.com \
--cc=hare@suse.de \
--cc=jbottomley@odin.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.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.