From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Bart Van Assche <Bart.VanAssche@sandisk.com>,
"hch\@lst.de" <hch@lst.de>,
"linux-block\@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Block device integrity support
Date: Fri, 02 Jun 2017 18:26:55 -0400 [thread overview]
Message-ID: <yq1h8zyhvps.fsf@oracle.com> (raw)
In-Reply-To: <703036c0-a5d2-f1df-4eb9-d0c46a30dce7@kernel.dk> (Jens Axboe's message of "Fri, 2 Jun 2017 15:24:31 -0700")
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
next prev parent reply other threads:[~2017-06-02 22:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 21:53 Block device integrity support Bart Van Assche
2017-06-02 22:24 ` Jens Axboe
2017-06-02 22:26 ` Martin K. Petersen [this message]
2017-06-02 22:24 ` Martin K. Petersen
2017-06-02 22:38 ` Bart Van Assche
2017-06-02 22:52 ` Jens Axboe
2017-06-03 7:32 ` Christoph Hellwig
2017-06-03 13:37 ` Jens Axboe
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=yq1h8zyhvps.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Bart.VanAssche@sandisk.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox