From: Karel Zak <kzak@redhat.com>
To: Bernhard Voelker <mail@bernhard-voelker.de>
Cc: Ludwig Nussel <ludwig.nussel@suse.de>, util-linux@vger.kernel.org
Subject: Re: [PATCH] remove obsolete encryption support from losetup
Date: Wed, 12 Sep 2012 14:52:48 +0200 [thread overview]
Message-ID: <20120912125248.GD17256@x2.net.home> (raw)
In-Reply-To: <1098712216.1298354.1347356412043.JavaMail.open-xchange@email.1und1.de>
On Tue, Sep 11, 2012 at 11:40:11AM +0200, Bernhard Voelker wrote:
> I think there are still a few fragments left, aren't there?
> At least in include/loopdev.h, in lib/loopdev.c and in
Well, this is API for kernel struct loop_info64 and we still prints
info about encrypted loopdevs in losetup output.
> tests/ts/mount/ecrypted.
Good point. Removed. Thanks.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2012-09-12 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 8:04 [PATCH] remove obsolete encryption support from losetup Ludwig Nussel
2012-09-11 8:49 ` Karel Zak
2012-09-11 9:40 ` Bernhard Voelker
2012-09-12 12:52 ` Karel Zak [this message]
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=20120912125248.GD17256@x2.net.home \
--to=kzak@redhat.com \
--cc=ludwig.nussel@suse.de \
--cc=mail@bernhard-voelker.de \
--cc=util-linux@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;
as well as URLs for NNTP newsgroup(s).