[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54e7ee75-6035-c2e9-fb8b-fe96adbb571a@linaro.org>
Date: Fri, 10 Mar 2023 11:03:45 +0000
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Miquel Raynal <miquel.raynal@...tlin.com>,
linux-kernel@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Michael Walle <michael@...le.cc>,
Rafał Miłecki <rafal@...ecki.pl>,
Robert Marko <robert.marko@...tura.hr>,
Luka Perkov <luka.perkov@...tura.hr>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
devicetree@...r.kernel.org
Subject: Re: [PATCH v3 17/20] nvmem: layouts: sl28vpd: Add new layout driver
On 08/03/2023 15:31, Miquel Raynal wrote:
> +
> +static int __init sl28vpd_init(void)
> +{
> + return nvmem_layout_register(&sl28vpd_layout);
> +}
> +
> +static void __exit sl28vpd_exit(void)
> +{
> + nvmem_layout_unregister(&sl28vpd_layout);
> +}
> +
> +module_init(sl28vpd_init);
> +module_exit(sl28vpd_exit);
Looking at this pattern in two drivers, we could come up with some
helper macro like.
#define module_nvmem_layout_driver(__layout_driver) \
module_driver(__layout_driver, nvmem_layout_register, \
nvmem_layout_unregister)
--srini
Powered by blists - more mailing lists