From: Valdis.Kletnieks@vt.edu
To: Mandeep Singh Baines <msb@chromium.org>
Cc: dm-devel@redhat.com, Will Drewry <wad@chromium.org>,
Elly Jones <ellyjones@chromium.org>,
Alasdair G Kergon <agk@redhat.com>, Milan Broz <mbroz@redhat.com>,
Olof Johansson <olofj@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dm: verity target
Date: Fri, 16 Sep 2011 13:54:07 -0400 [thread overview]
Message-ID: <59032.1316195647@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 15 Sep 2011 11:45:59 PDT." <1316112359-6085-1-git-send-email-msb@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
On Thu, 15 Sep 2011 11:45:59 PDT, Mandeep Singh Baines said:
> The verity target provides transparent integrity checking of block devices
> using a cryptographic digest.
I just had this mental image of Dr Henry Jones saying: "But in Latin, verify is
spelled with an f..." ;)
Might want to add something to device-mapper/dm-verity.txt explaining
where the name came from and that it's *not* a typo?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-09-16 17:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 18:45 Mandeep Singh Baines
2011-09-16 17:54 ` Valdis.Kletnieks [this message]
2011-09-27 19:02 ` Will Drewry
2011-09-27 19:13 ` Alasdair G Kergon
2011-09-27 19:31 ` Will Drewry
2011-09-28 21:30 ` Valdis.Kletnieks
2011-09-29 1:07 ` John Stoffel
2011-09-29 17:31 ` Mandeep Singh Baines
2011-09-15 22:02 Wesley Miaw
2011-11-10 5:18 Mandeep Singh Baines
2011-11-10 7:44 ` Steffen Klassert
2011-11-10 14:42 ` Will Drewry
2011-12-22 0:36 Mandeep Singh Baines
2012-01-04 21:49 Mandeep Singh Baines
2012-01-04 22:42 ` Mandeep Singh Baines
2012-02-28 22:57 Mandeep Singh Baines
2012-02-29 21:16 ` Mikulas Patocka
2012-03-01 6:24 ` Mandeep Singh Baines
2012-02-29 21:30 ` Andrew Morton
2012-03-02 0:33 Mandeep Singh Baines
2012-03-02 16:08 ` Mandeep Singh Baines
2012-03-10 0:03 Mandeep Singh Baines
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=59032.1316195647@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ellyjones@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=msb@chromium.org \
--cc=olofj@chromium.org \
--cc=wad@chromium.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
all inboxes | Powered by JetHome®