From: "Ma, Jun" <majun@amd.com>
To: Guenter Roeck <linux@roeck-us.net>, Ma Jun <Jun.Ma2@amd.com>,
jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: majun@amd.com
Subject: Re: [PATCH] hwmon: Add a new macro sensor_sysfs_attr
Date: Fri, 10 Nov 2023 09:15:11 +0800 [thread overview]
Message-ID: <50372d43-f89e-4969-a609-d8e1ff2afdf6@amd.com> (raw)
In-Reply-To: <0ae6bcc2-a30d-4840-a21a-0de0b394c309@roeck-us.net>
Hi Guenter,
On 11/9/2023 1:28 PM, Guenter Roeck wrote:
> On 11/8/23 21:14, Ma Jun wrote:
>> The attribute definiations like &sensor_dev_attr_xx_xx.dev_attr.attr
>> are widely used in drivers. So add a new macro sensor_sysfs_attr t
>> to make it easier to understand and use.
>>
>> For example, user can use the sensor_sysfs_attr(xx_xx) instead of
>> &sensor_dev_attr_xx_xx.dev_attr.attr
>>
>> Signed-off-by: Ma Jun <Jun.Ma2@amd.com>
>> ---
>> include/linux/hwmon-sysfs.h | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/include/linux/hwmon-sysfs.h b/include/linux/hwmon-sysfs.h
>> index d896713359cd..7feae637e3b5 100644
>> --- a/include/linux/hwmon-sysfs.h
>> +++ b/include/linux/hwmon-sysfs.h
>> @@ -14,6 +14,10 @@ struct sensor_device_attribute{
>> struct device_attribute dev_attr;
>> int index;
>> };
>> +
>> +#define to_sensor_sysfs_attr(_name) \
>> + (&sensor_dev_attr_##_name.dev_attr.attr)
>> +
>> #define to_sensor_dev_attr(_dev_attr) \
>> container_of(_dev_attr, struct sensor_device_attribute, dev_attr)
>>
>
> No. This would just invite people to submit patches converting existing code
> to use this new macro. Instead of providing macros to support deprecated APIs,
> convert drivers to use an API which is not deprecated. This would for the
Which API is not deprecated do you mean?
Regards,
Ma Jun
> most part avoid the need for including hwmon-sysfs.h in the first place and
> at the same time reduce driver code size significantly.
>
> Guenter
>
next prev parent reply other threads:[~2023-11-10 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 5:14 Ma Jun
2023-11-09 5:28 ` Guenter Roeck
2023-11-10 1:15 ` Ma, Jun [this message]
2023-11-10 2:50 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50372d43-f89e-4969-a609-d8e1ff2afdf6@amd.com \
--to=majun@amd.com \
--cc=Jun.Ma2@amd.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®