[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YkRiBAyw2DhIOitg@lunn.ch>
Date: Wed, 30 Mar 2022 15:58:28 +0200
From: Andrew Lunn <andrew@...n.ch>
To: David Laight <David.Laight@...lab.com>
Cc: 'Guenter Roeck' <linux@...ck-us.net>,
'Michael Walle' <michael@...le.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-hwmon@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 1/5] hwmon: introduce hwmon_sanitize_name()
> So why not error the request to created the hwmon device with
> an invalid name.
> The name supplied will soon get fixed - since it is a literal
> string in the calling driver.
It is often not a literal string in the driver, but something based on
the DT description of the hardware.
Andrew
Powered by blists - more mailing lists