[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220405092452.4033674-1-michael@walle.cc>
Date: Tue, 5 Apr 2022 11:24:50 +0200
From: Michael Walle <michael@...le.cc>
To: Xu Yilun <yilun.xu@...el.com>, Tom Rix <trix@...hat.com>,
Jean Delvare <jdelvare@...e.com>,
Guenter Roeck <linux@...ck-us.net>,
Andrew Lunn <andrew@...n.ch>,
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>
Cc: linux-hwmon@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, David Laight <David.Laight@...LAB.COM>,
Michael Walle <michael@...le.cc>
Subject: [PATCH v4 0/2] hwmon: introduce hwmon_sanitize()
During development of the support for the temperature sensor on the GPY
PHY, I've noticed that there is ususually a loop over the name to
replace any invalid characters. Instead of open coding it in the drivers
provide a convenience function.
changes since v3:
- don't return NULL but ERR_PTR(-ENOMEM)
- check !dev in devm_ variant
changes since v2:
- doc update
- dropped last three patches, the net patches will be submitted
seperately
changes since v1:
- split patches
- add hwmon-kernel-api.rst documentation
- move the strdup into the hwmon core
- also provide a resource managed variant
Michael Walle (2):
hwmon: introduce hwmon_sanitize_name()
hwmon: intel-m10-bmc-hwmon: use devm_hwmon_sanitize_name()
Documentation/hwmon/hwmon-kernel-api.rst | 16 +++++++
drivers/hwmon/hwmon.c | 53 ++++++++++++++++++++++++
drivers/hwmon/intel-m10-bmc-hwmon.c | 11 ++---
include/linux/hwmon.h | 3 ++
4 files changed, 75 insertions(+), 8 deletions(-)
--
2.30.2
Powered by blists - more mailing lists