From: Andrew Lunn <andrew@lunn.ch>
To: Huisong Li <lihuisong@huawei.com>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, netdev@vger.kernel.org,
linux-rtc@vger.kernel.org, oss-drivers@corigine.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, louis.peens@corigine.com,
hkallweit1@gmail.com, linux@armlinux.org.uk, kabel@kernel.org,
alexandre.belloni@bootlin.com, krzk@kernel.org,
zhanjie9@hisilicon.com, zhenglifeng1@huawei.com,
liuyonglong@huawei.com
Subject: Re: [PATCH v1 0/9] Use HWMON_CHANNEL_INFO macro to simplify code
Date: Fri, 24 Jan 2025 16:08:22 +0100 [thread overview]
Message-ID: <fca9ca93-16e4-44db-8fbb-90bc6af952e7@lunn.ch> (raw)
In-Reply-To: <20250124022635.16647-1-lihuisong@huawei.com>
On Fri, Jan 24, 2025 at 10:26:26AM +0800, Huisong Li wrote:
> The HWMON_CHANNEL_INFO macro is provided by hwmon.h and used widely by many
> other drivers. This series use HWMON_CHANNEL_INFO macro to simplify code.
>
> Huisong Li (9):
> media: video-i2c: Use HWMON_CHANNEL_INFO macro to simplify code
> net: aquantia: Use HWMON_CHANNEL_INFO macro to simplify code
> net: nfp: Use HWMON_CHANNEL_INFO macro to simplify code
> net: phy: marvell: Use HWMON_CHANNEL_INFO macro to simplify code
> net: phy: marvell10g: Use HWMON_CHANNEL_INFO macro to simplify code
> rtc: ab-eoz9: Use HWMON_CHANNEL_INFO macro to simplify code
> rtc: ds3232: Use HWMON_CHANNEL_INFO macro to simplify code
> w1: w1_therm: w1: Use HWMON_CHANNEL_INFO macro to simplify code
> net: phy: aquantia: Use HWMON_CHANNEL_INFO macro to simplify code
Please split these patches per subsystem. Maintainers generally have
scripts to accept patches, and those scripts don't work when there are
patches for other Maintainers mixed in. So you need 4 patchsets,
media, net, rtc and w1.
I would also like to see the HWMON Maintainers opinion on these. A
patchset containing these have already been NACKed once. These patches
do however look like valid cleanups. But are they just so you can do
something bad in your vendor tree, which will never make it to
mainline?
Andrew
next prev parent reply other threads:[~2025-01-24 15:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 2:26 [PATCH v1 0/9] Use HWMON_CHANNEL_INFO macro to simplify code Huisong Li
2025-01-24 2:26 ` [PATCH v1 1/9] media: video-i2c: " Huisong Li
2025-01-24 2:26 ` [PATCH v1 2/9] net: aquantia: " Huisong Li
2025-01-24 2:26 ` [PATCH v1 3/9] net: nfp: " Huisong Li
2025-01-24 2:26 ` [PATCH v1 4/9] net: phy: marvell: " Huisong Li
2025-01-24 2:26 ` [PATCH v1 5/9] net: phy: marvell10g: " Huisong Li
2025-01-24 2:26 ` [PATCH v1 6/9] rtc: ab-eoz9: " Huisong Li
2025-01-24 2:26 ` [PATCH v1 7/9] rtc: ds3232: " Huisong Li
2025-01-24 2:26 ` [PATCH v1 8/9] w1: w1_therm: w1: " Huisong Li
2025-02-03 11:56 ` (subset) " Krzysztof Kozlowski
2025-02-05 2:10 ` lihuisong (C)
2025-01-24 2:26 ` [PATCH v1 9/9] net: phy: aquantia: " Huisong Li
2025-01-24 15:08 ` Andrew Lunn [this message]
2025-01-24 15:41 ` [PATCH v1 0/9] " Guenter Roeck
2025-02-05 2:08 ` lihuisong (C)
2025-02-05 2:05 ` lihuisong (C)
2025-01-24 16:58 ` Krzysztof Kozlowski
2025-02-05 1:55 ` 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=fca9ca93-16e4-44db-8fbb-90bc6af952e7@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=irusskikh@marvell.com \
--cc=kabel@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=lihuisong@huawei.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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=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