linux-kernel - Re: [PATCH V3] leds: pca955x: Add ACPI support for pca955x

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: <959f287f-74c1-d790-4f36-9c7ac053bc8e@axentia.se>
Date:   Wed, 30 Nov 2016 10:36:51 +0100
From:   Peter Rosin <peda@...ntia.se>
To:     Phong Vo <pvo@....com>, Jacek Anaszewski <j.anaszewski@...sung.com>
CC:     Mika Westerberg <mika.westerberg@...ux.intel.com>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Richard Purdie <rpurdie@...ys.net>,
        <linux-leds@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-acpi@...r.kernel.org>, Loc Ho <lho@....com>,
        Thang Nguyen <tqnguyen@....com>, patches <patches@....com>,
        Tin Huynh <tnhuynh@....com>
Subject: Re: [PATCH V3] leds: pca955x: Add ACPI support for pca955x

On 2016-11-30 10:10, Phong Vo wrote:
> +-----Original Message-----
> +From: Jacek Anaszewski [mailto:j.anaszewski@...sung.com]
> +
> +Hi Phong,
> +
> +On 11/30/2016 09:23 AM, Phong Vo wrote:
> +> +-----Original Message-----
> +> +From: Jacek Anaszewski [mailto:j.anaszewski@...sung.com]
> +> +
> +> +On 11/30/2016 09:06 AM, Tin Huynh wrote:
> +> +> On Wed, Nov 30, 2016 at 3:01 PM, Jacek Anaszewski <j.anaszewski@...sung.com> wrote:
> +> +>> On 11/30/2016 08:51 AM, Jacek Anaszewski wrote:
> +> +>>> On 11/30/2016 04:08 AM, Tin Huynh wrote:
> +> +>>>> +static const struct acpi_device_id pca955x_acpi_ids[] = {
> +> +>>>> +    { .id = "PCA9550", .driver_data = pca9550 },
> +> +>>>> +    { .id = "PCA9551", .driver_data = pca9551 },
> +> +>>>> +    { .id = "PCA9552", .driver_data = pca9552 },
> +> +>>>> +    { .id = "PCA9553", .driver_data = pca9553 },
> +> +>>>> +    { }
> +> +>>
> +> +>>
> +> +>> OK, I see that you brought back explicit properties in the
> +> +>> structure initializer. Is there some vital reason for that?
> +>
> +> It's not vital, but to make it consistent with what was done for
> +> pca963x,
> +
> +For pca963x I applied the version without explicit properties.
> +Note that this is consistent with pca963x_id array above the added
> +pca963x_acpi_ids. For pca955x the situation is the same.
> +
> +> and also per suggestion by Mika on reviewing  a different driver
> +> mux:954x in another thread.
> +
> +Could you give a reference to that thread? In the review of V1 of this
> +patch Mika mentioned "{ "PCA9553", pca9553 }" scheme.
> +
> 
> Actually it was Peter Rosin (not Mika) on linux-i2c and the reference to
> that is follows
> 
> https://lkml.org/lkml/2016/11/18/732
> 
> I am including Robin here.

I tried to say that I *personally* would have added the explicit
field specifiers but that it didn't seem like the norm and that both
of the approaches would therefore be perfectly ok by me (as there are
other examples of acpi id table initializers with field specifiers).

To sum up, I don't really care. But my question lingers, is there some
compelling reason to not have the explicit field specifiers?

Cheers,
Peter