On 09/10/2014 06:23 PM, Martin K. Petersen wrote:
>> "Jens" == Jens Axboe writes:
>
> Jens> Thanks, I'll do that once Martin respins the previous series (was
> Jens> pulled due to multiple issues).
>
> I bumped bi_rw to u64 as discussed. Will get that into -next to see if
> there's any fallo
> "Jens" == Jens Axboe writes:
Jens> Thanks, I'll do that once Martin respins the previous series (was
Jens> pulled due to multiple issues).
I bumped bi_rw to u64 as discussed. Will get that into -next to see if
there's any fallout.
--
Martin K. Petersen Oracle Linux Engineering
--
To
On 09/07/2014 10:29 AM, Christoph Hellwig wrote:
> On Thu, Aug 28, 2014 at 02:10:49PM -0600, Jens Axboe wrote:
>> On 08/28/2014 01:31 PM, Martin K. Petersen wrote:
>>> This is the data integrity patch series originally submitted for 3.16
>>> and 3.17. It has been rebased on top of block/for-3.18/c
On Thu, Aug 28, 2014 at 02:10:49PM -0600, Jens Axboe wrote:
> On 08/28/2014 01:31 PM, Martin K. Petersen wrote:
> > This is the data integrity patch series originally submitted for 3.16
> > and 3.17. It has been rebased on top of block/for-3.18/core. Other
> > than that there are no changes from
On Thu, Aug 28, 2014 at 02:10:49PM -0600, Jens Axboe wrote:
> On 08/28/2014 01:31 PM, Martin K. Petersen wrote:
> > This is the data integrity patch series originally submitted for 3.16
> > and 3.17. It has been rebased on top of block/for-3.18/core. Other
> > than that there are no changes from
On 08/28/2014 01:31 PM, Martin K. Petersen wrote:
> This is the data integrity patch series originally submitted for 3.16
> and 3.17. It has been rebased on top of block/for-3.18/core. Other
> than that there are no changes from v2.
Thanks, picked up. I did not apply 14/14 since that should go t
This is the data integrity patch series originally submitted for 3.16
and 3.17. It has been rebased on top of block/for-3.18/core. Other
than that there are no changes from v2.
--
Martin K. Petersen Oracle Linux Engineering
--
To unsubscribe from this list: send the line "unsubscribe linu
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 majord...@vger.kernel.
> "Christoph" == Christoph Hellwig 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 this. But
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 "unsubscri
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.
- bi_specia
Here's an update to the block layer and SCSI data integrity code. There
are a whole bunch of cleanups, some as a result of the work that Kent
did to the block layer a while back. A bunch of dead code is removed,
mainly the tagging functionality that nobody ended up using.
There's also some prep wo
12 matches
Mail list logo
