[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37ffd544-5f83-3a4e-3db1-b774684d5fe8@free-electrons.com>
Date: Tue, 26 Jul 2016 09:55:02 +0200
From: Quentin Schulz <quentin.schulz@...e-electrons.com>
To: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
Cc: jdelvare@...e.com, linux@...ck-us.net, jic23@...nel.org,
knaack.h@....de, lars@...afoo.de, pmeerw@...erw.net,
maxime.ripard@...e-electrons.com, wens@...e.org,
lee.jones@...aro.org, linux-kernel@...r.kernel.org,
linux-hwmon@...r.kernel.org, linux-iio@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
antoine.tenart@...e-electrons.com
Subject: Re: [PATCH v3 1/4] hwmon: iio_hwmon: delay probing with late_initcall
Hi,
On 26/07/2016 09:48, Thomas Petazzoni wrote:
> Hello,
>
> On Tue, 26 Jul 2016 09:43:44 +0200, Quentin Schulz wrote:
>
>> -module_platform_driver(iio_hwmon_driver);
>> +static struct platform_driver * const drivers[] = {
>> + &iio_hwmon_driver,
>> +};
>> +
>> +static int __init iio_hwmon_late_init(void)
>> +{
>> + return platform_register_drivers(drivers, ARRAY_SIZE(drivers));
>
> Why not platform_register_driver() ?
>
> This would avoid the need to declare an array with just one entry.
Actually, it is named platform_driver_register() as you just showed me
and that's the reason I didn't find it under platform_register_driver().
Thanks!
Quentin
Powered by blists - more mailing lists