[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <9B742DB5-F584-4A47-A04B-4F72EB17519C@holtmann.org>
Date: Mon, 15 Oct 2018 20:06:02 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: Matthias Kaehlcke <mka@...omium.org>
Cc: Sinan Kaya <okaya@...eaurora.org>,
Balakrishna Godavarthi <bgodavar@...eaurora.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Marcin Wojtas <mw@...ihalf.com>,
Andy Shevchenko Andy Shevchenko <andy.shevchenko@...il.com>,
Johan Hedberg <johan.hedberg@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Bluez mailing list <linux-bluetooth@...r.kernel.org>,
Loic Poulain <loic.poulain@...aro.org>,
Brian Norris <briannorris@...omium.org>
Subject: Re: [PATCH v4 1/2] Bluetooth: Add device_get_bd_address()
Hi Matthias,
>>>> void bt_sock_reclassify_lock(struct sock *sk, int proto);
>>>>
>>>> +int device_get_bd_address(struct device *dev, bdaddr_t *bd_addr);
>>>
>>> Maybe change the API name to start with bt_ and get rid of device_?
>>
>> device_ indicates that we get the BD_ADDR for a 'struct device' and
>> not for e.g. a 'struct fwnode_handle'.
>>
>> Anyway with this version of the patch fwnode_get_bd_address() has been
>> scrapped and it might never be introduced again, so I'm open to change
>> the name to bt_ if there is a general preference for it.
>
> Marcel, can you live with this being added to the Bluetooth code base
> instead of property? Also if you'd prefer the function to be named
> bt_get_bd_address() let me know.
explain to me again why this is useful? I am failing to see the benefit if this is not part of the property.h API.
Regards
Marcel
Powered by blists - more mailing lists