linux-kernel - Re: [RFC PATCH v2 4/8] block: implement NVMEM provider

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <palxzjqvvteqajsajrdgdvncq3eka65pq7de4jnwyhpfs3xrac@c34xcdxctbcq>
Date: Wed, 6 Mar 2024 09:00:12 -0300
From: "Ricardo B. Marliere" <ricardo@...liere.net>
To: Daniel Golle <daniel@...rotopia.org>
Cc: Rob Herring <robh@...nel.org>, 
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>, 
	Ulf Hansson <ulf.hansson@...aro.org>, Jens Axboe <axboe@...nel.dk>, Dave Chinner <dchinner@...hat.com>, 
	Jan Kara <jack@...e.cz>, Thomas Weißschuh <linux@...ssschuh.net>, 
	Christian Brauner <brauner@...nel.org>, Li Lingfeng <lilingfeng3@...wei.com>, 
	Damien Le Moal <dlemoal@...nel.org>, Min Li <min15.li@...sung.com>, 
	Adrian Hunter <adrian.hunter@...el.com>, Hannes Reinecke <hare@...e.de>, 
	Christian Loehle <CLoehle@...erstone.com>, Avri Altman <avri.altman@....com>, Bean Huo <beanhuo@...ron.com>, 
	Yeqi Fu <asuk4.q@...il.com>, Victor Shih <victor.shih@...esyslogic.com.tw>, 
	Christophe JAILLET <christophe.jaillet@...adoo.fr>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org, 
	linux-block@...r.kernel.org, Diping Zhang <diping.zhang@...inet.com>, 
	Jianhui Zhao <zhaojh329@...il.com>, Jieying Zeng <jieying.zeng@...inet.com>, 
	Chad Monroe <chad.monroe@...ran.com>, Adam Fox <adam.fox@...ran.com>, John Crispin <john@...ozen.org>
Subject: Re: [RFC PATCH v2 4/8] block: implement NVMEM provider

Hi Daniel,

On  5 Mar 20:23, Daniel Golle wrote:
> static int __init blk_nvmem_init(void)
> {
> 	int ret;
>  
> 	ret = class_interface_register(&blk_nvmem_bus_interface);
> 	if (ret)
> 		return ret;
>  
> 	return 0;

Just an idea, why not just:

return class_interface_register(&blk_nvmem_bus_interface);