Re: Block/SCSI data integrity update v2

2014-07-29 Thread Christoph Hellwig
Sami, can you review the remaining patches in the series so that it's ready to be included in the scsi tree once Jens decides he is fine with that? Thanks, Christoph -- To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to

Re: Block/SCSI data integrity update v2

2014-07-26 Thread Christoph Hellwig
I haven't done an in-depth review of the whole series, but it looks generally good to me. How should we pull it in? Normally block stuff should go through Jens, but the sd changes won't apply without the various patches in the scsi tree. -- To unsubscribe from this list: send the line

Re: Block/SCSI data integrity update v2

2014-07-26 Thread Martin K. Petersen
Christoph == Christoph Hellwig h...@infradead.org writes: Christoph How should we pull it in? Normally block stuff should go Christoph through Jens, but the sd changes won't apply without the Christoph various patches in the scsi tree. Typically Jens and James stagger their merges when we do

Block/SCSI data integrity update v2

2014-07-25 Thread Martin K. Petersen
This is the data integrity patch series originally submitted for 3.16. It has been rebased on top of the current 3.17 SCSI queue tree. I believe I have addressed all the changes requested in the reviews. Aside from a code cleanup in the sd prot_op code there are no functional changes. -