Linux Device Mapper development
 help / color / mirror / Atom feed
From: Loic Pefferkorn <loic@loicp.eu>
To: agk@redhat.com, snitzer@redhat.com
Cc: dm-devel@redhat.com
Subject: Re: [PATCH] Update CONFIG_DM_CRYPT help-text link
Date: Tue, 6 Jan 2015 20:15:09 +0100	[thread overview]
Message-ID: <20150106191509.GA15700@iron> (raw)
In-Reply-To: <81c1a7329d2146d37b22d7efa96b3a449cb66d14.1418677931.git.loic@loicp.eu>

On Mon, Dec 15, 2014 at 10:18:43PM +0100, Loic Pefferkorn wrote:
> Hello,
> 
> This patch fixes the obsolete help-text link of CONFIG_DM_CRYPT.
> Applies against next-20141215.
> 
> Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=75111
> 
> Signed-off-by: Loic Pefferkorn <loic@loicp.eu>
> ---
>  drivers/md/Kconfig | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig
> index 5bdedf6..09c89a4b 100644
> --- a/drivers/md/Kconfig
> +++ b/drivers/md/Kconfig
> @@ -230,9 +230,8 @@ config DM_CRYPT
>  	  transparently encrypts the data on it. You'll need to activate
>  	  the ciphers you're going to use in the cryptoapi configuration.
>  
> -	  Information on how to use dm-crypt can be found on
> -
> -	  <http://www.saout.de/misc/dm-crypt/>
> +	  For further information on dm-crypt and userspace tools see:
> +	  <http://code.google.com/p/cryptsetup/wiki/DMCrypt>
>  
>  	  To compile this code as a module, choose M here: the module will
>  	  be called dm-crypt.
> -- 
> 2.1.3
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
> 

Hello guys,

Just a gentle reminder, please tell me if something is wrong.

-- 
Cheers,
Loïc

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

      reply	other threads:[~2015-01-06 19:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 21:18 [PATCH] Update CONFIG_DM_CRYPT help-text link Loic Pefferkorn
2015-01-06 19:15 ` Loic Pefferkorn [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=20150106191509.GA15700@iron \
    --to=loic@loicp.eu \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=snitzer@redhat.com \
    /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