linux-kernel - Re: [PATCH] RAM block device support module name update in Kconfig

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <52A4AA04.6040507@infradead.org>
Date:	Sun, 08 Dec 2013 09:19:00 -0800
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Fabian Frederick <fabf@...net.be>, linux-kernel@...r.kernel.org
CC:	npiggin@...il.com, axboe <axboe@...nel.dk>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] RAM block device support module name update in Kconfig

On 12/06/13 05:38, Fabian Frederick wrote:
> RAM block device support module name changed to brd.ko 
> some years ago with an "rd" alias to match previous module implementation.
> This patch updates its Kconfig definition.
> 
> Signed-off-by: Fabian Frederick <fabf@...net.be>

I haven't seen any activity from Nick lately.
Let's Cc: Jens and Andrew.

Acked-by: Randy Dunlap <rdunlap@...radead.org>

Thanks.

> ---
>  drivers/block/Kconfig | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
> index 86b9f37..9ffa90c 100644
> --- a/drivers/block/Kconfig
> +++ b/drivers/block/Kconfig
> @@ -368,7 +368,8 @@ config BLK_DEV_RAM
>  	  For details, read <file:Documentation/blockdev/ramdisk.txt>.
>  
>  	  To compile this driver as a module, choose M here: the
> -	  module will be called rd.
> +	  module will be called brd. An alias "rd" has been defined
> +	  for historical reasons.
>  
>  	  Most normal users won't need the RAM disk functionality, and can
>  	  thus say N here.
> --



-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/