Re: Block device integrity support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jens Axboe <axboe@xxxxxxxxx>
Subject: Re: Block device integrity support
From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
Date: Fri, 02 Jun 2017 18:26:55 -0400
Cc: Bart Van Assche <Bart.VanAssche@xxxxxxxxxxx>, "hch\@lst.de" <hch@xxxxxx>, "linux-block\@vger.kernel.org" <linux-block@xxxxxxxxxxxxxxx>
In-reply-to: <703036c0-a5d2-f1df-4eb9-d0c46a30dce7@kernel.dk> (Jens Axboe's message of "Fri, 2 Jun 2017 15:24:31 -0700")
Organization: Oracle Corporation
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)

Jens,

> There's not much in my for-next/4.13 branches yet, so I'm assuming this also
> triggers with current mainline?

Yep.

-- 
Martin K. Petersen	Oracle Linux Engineering

References:
- Block device integrity support
  - From: Bart Van Assche
- Re: Block device integrity support
  - From: Jens Axboe

Prev by Date: Re: Block device integrity support
Next by Date: Re: [PATCH v3 3/9] blk-mq: use the introduced blk_mq_unquiesce_queue()
Previous by thread: Re: Block device integrity support
Next by thread: Re: Block device integrity support
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux