Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: "lihuisong (C)" <lihuisong@huawei.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: <linux-hwmon@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	<linux-media@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<arm-scmi@vger.kernel.org>, Netdev <netdev@vger.kernel.org>,
	<linux-rtc@vger.kernel.org>, <oss-drivers@corigine.com>,
	<linux-rdma@vger.kernel.org>,
	<platform-driver-x86@vger.kernel.org>, <linuxarm@huawei.com>,
	<linux@roeck-us.net>, <jdelvare@suse.com>, <kernel@maidavale.org>,
	<pauk.denis@gmail.com>, <james@equiv.tech>,
	<sudeep.holla@arm.com>, <cristian.marussi@arm.com>,
	<matt@ranostay.sg>, <mchehab@kernel.org>, <irusskikh@marvell.com>,
	<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<saeedm@nvidia.com>, <leon@kernel.org>, <tariqt@nvidia.com>,
	<louis.peens@corigine.com>, <hkallweit1@gmail.com>,
	<linux@armlinux.org.uk>, <kabel@kernel.org>, <W_Armin@gmx.de>,
	Hans de Goede <hdegoede@redhat.com>,
	<alexandre.belloni@bootlin.com>, <krzk@kernel.org>,
	<jonathan.cameron@huawei.com>, <zhanjie9@hisilicon.com>,
	<zhenglifeng1@huawei.com>, <liuyonglong@huawei.com>
Subject: Re: [PATCH v1 19/21] platform/x86: dell-ddv: Fix the type of 'config' in struct hwmon_channel_info to u64
Date: Wed, 22 Jan 2025 13:57:51 +0800	[thread overview]
Message-ID: <ef34bf8a-c8d9-13bb-011c-6a4365bb3cb8@huawei.com> (raw)
In-Reply-To: <844c5097-eeb7-7275-7558-83ca4e5ee4b2@linux.intel.com>


在 2025/1/21 20:18, Ilpo Järvinen 写道:
> On Tue, 21 Jan 2025, Huisong Li wrote:
>
>> The type of 'config' in struct hwmon_channel_info has been fixed to u64.
>> Modify the related code in driver to avoid compiling failure.
> Does this mean that after applying part of your series but not yet this
> patch, compile would fail? If so, it's unacceptable. At no point in a
> patch series are you allowed to cause a compile failure because it hinders
> 'git bisect' that is an important troubleshooting tool.
>
> So you might have to combine changes to drivers and API if you make an
> API change that breaks driver build until driver too is changed. Note that
> it will impact a lot how quickly your patches can be accepted as much
> higher level of coordination is usually required if your patch is touching
> things all over the place, but it cannot be avoided at times. And
> requirement of doing minimal change only will be much much higher in such
> a large scale change.
>
Ack. Thanks for your reply.
>
>> Signed-off-by: Huisong Li <lihuisong@huawei.com>
>> ---
>>   drivers/platform/x86/dell/dell-wmi-ddv.c | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/platform/x86/dell/dell-wmi-ddv.c b/drivers/platform/x86/dell/dell-wmi-ddv.c
>> index e75cd6e1efe6..efb2278aabb9 100644
>> --- a/drivers/platform/x86/dell/dell-wmi-ddv.c
>> +++ b/drivers/platform/x86/dell/dell-wmi-ddv.c
>> @@ -86,7 +86,7 @@ struct thermal_sensor_entry {
>>   
>>   struct combined_channel_info {
>>   	struct hwmon_channel_info info;
>> -	u32 config[];
>> +	u64 config[];
>>   };
>>   
>>   struct combined_chip_info {
>> @@ -500,7 +500,7 @@ static const struct hwmon_ops dell_wmi_ddv_ops = {
>>   
>>   static struct hwmon_channel_info *dell_wmi_ddv_channel_create(struct device *dev, u64 count,
>>   							      enum hwmon_sensor_types type,
>> -							      u32 config)
>> +							      u64 config)
>>   {
>>   	struct combined_channel_info *cinfo;
>>   	int i;
>> @@ -543,7 +543,7 @@ static struct hwmon_channel_info *dell_wmi_ddv_channel_init(struct wmi_device *w
>>   							    struct dell_wmi_ddv_sensors *sensors,
>>   							    size_t entry_size,
>>   							    enum hwmon_sensor_types type,
>> -							    u32 config)
>> +							    u64 config)
>>   {
>>   	struct hwmon_channel_info *info;
>>   	int ret;
>>
> .

  reply	other threads:[~2025-01-22  5:57 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21  6:44 [PATCH v1 00/21] hwmon: Fix the type of 'config' in struct hwmon_channel_info to u64 Huisong Li
2025-01-21  6:44 ` [PATCH v1 01/21] " Huisong Li
2025-01-21 17:05   ` Russell King (Oracle)
2025-01-21 17:32     ` Guenter Roeck
2025-01-22  3:34     ` lihuisong (C)
2025-01-21  6:45 ` [PATCH v1 02/21] media: video-i2c: Use HWMON_CHANNEL_INFO macro to simplify code Huisong Li
2025-01-21  6:45 ` [PATCH v1 03/21] net: aquantia: " Huisong Li
2025-01-21  6:45 ` [PATCH v1 04/21] net: nfp: " Huisong Li
2025-01-21  6:45 ` [PATCH v1 05/21] net: phy: marvell: " Huisong Li
2025-01-21  6:45 ` [PATCH v1 06/21] net: phy: marvell10g: " Huisong Li
2025-01-21  6:45 ` [PATCH v1 07/21] rtc: ab-eoz9: " Huisong Li
2025-01-21  6:45 ` [PATCH v1 08/21] rtc: ds3232: " Huisong Li
2025-01-21  6:45 ` [PATCH v1 09/21] w1: w1_therm: w1: " Huisong Li
2025-01-21  6:45 ` [PATCH v1 10/21] net: phy: aquantia: " Huisong Li
2025-01-21  6:45 ` [PATCH v1 11/21] hwmon: (asus_wmi_sensors) Fix type of 'config' in struct hwmon_channel_info to u64 Huisong Li
2025-01-21  6:45 ` [PATCH v1 12/21] hwmon: (hp-wmi-sensors) " Huisong Li
2025-01-21  6:45 ` [PATCH v1 13/21] hwmon: (mr75203) Fix the " Huisong Li
2025-01-21  6:45 ` [PATCH v1 14/21] hwmon: (pwm-fan) " Huisong Li
2025-01-21  6:45 ` [PATCH v1 15/21] hwmon: (scmi-hwmon) " Huisong Li
2025-01-21  6:45 ` [PATCH v1 16/21] hwmon: (tmp401) " Huisong Li
2025-01-21  6:45 ` [PATCH v1 17/21] hwmon: (tmp421) " Huisong Li
2025-01-21  6:45 ` [PATCH v1 18/21] net/mlx5: " Huisong Li
2025-01-21  6:45 ` [PATCH v1 19/21] platform/x86: dell-ddv: " Huisong Li
2025-01-21 12:18   ` Ilpo Järvinen
2025-01-22  5:57     ` lihuisong (C) [this message]
2025-01-21  6:45 ` [PATCH v1 20/21] hwmon: (asus-ec-sensors) " Huisong Li
2025-01-21  6:45 ` [PATCH v1 21/21] hwmon: (lm90) " Huisong Li
2025-01-21  7:47 ` [PATCH v1 00/21] hwmon: " Krzysztof Kozlowski
2025-01-21  8:14   ` lihuisong (C)
2025-01-22  7:51     ` Krzysztof Kozlowski
2025-01-22 14:36       ` Guenter Roeck
2025-01-21 14:12 ` Armin Wolf
2025-01-21 14:50   ` Guenter Roeck
2025-01-21 17:20     ` Russell King (Oracle)
2025-01-21 17:37       ` Guenter Roeck
2025-01-22  4:06       ` lihuisong (C)
2025-01-22  2:52     ` lihuisong (C)
2025-01-22  3:19       ` Guenter Roeck
2025-01-22  3:36         ` lihuisong (C)
2025-01-22  2:34   ` lihuisong (C)

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=ef34bf8a-c8d9-13bb-011c-6a4365bb3cb8@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=W_Armin@gmx.de \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=arm-scmi@vger.kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hdegoede@redhat.com \
    --cc=hkallweit1@gmail.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=irusskikh@marvell.com \
    --cc=james@equiv.tech \
    --cc=jdelvare@suse.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=kabel@kernel.org \
    --cc=kernel@maidavale.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@roeck-us.net \
    --cc=linuxarm@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=louis.peens@corigine.com \
    --cc=matt@ranostay.sg \
    --cc=mchehab@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.com \
    --cc=pabeni@redhat.com \
    --cc=pauk.denis@gmail.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=sudeep.holla@arm.com \
    --cc=tariqt@nvidia.com \
    --cc=zhanjie9@hisilicon.com \
    --cc=zhenglifeng1@huawei.com \
    /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