[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ab64105b-c48d-cdf2-598a-3e0a2e261b27@roeck-us.net>
Date: Mon, 28 Mar 2022 09:27:50 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Andrew Lunn <andrew@...n.ch>, Michael Walle <michael@...le.cc>
Cc: Xu Yilun <yilun.xu@...el.com>, Tom Rix <trix@...hat.com>,
Jean Delvare <jdelvare@...e.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, linux-hwmon@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v1 0/2] hwmon: introduce hwmon_sanitize()
On 3/28/22 05:56, Andrew Lunn wrote:
>> I'm not sure how to handle this correctly, as this touches both the
>> network tree and the hwmon tree. Also, the GPY PHY temperature senors
>> driver would use it.
>
> There are a few options:
>
> 1) Get the hwmon_sanitize_name() merged into hwmon, ask for a stable
> branch, and get it merged into netdev net-next.
>
> 2) Have the hwmon maintainers ACK the change and agree that it can be
> merged via netdev.
>
> Probably the second option is easiest, and since it is not touching
> the core of hwmon, it is unlikely to cause merge conflicts.
>
No, it isn't the easiest solution because it also modifies a hwmon
driver to use it.
Guenter
Powered by blists - more mailing lists