From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] hwmon w83627hf: add mfd support.
Date: Thu, 10 Sep 2009 12:56:09 +0000 [thread overview]
Message-ID: <20090910145609.200ee1f0@hyperion.delvare> (raw)
In-Reply-To: <1252585810-5336-2-git-send-email-giometti@linux.it>
Hi Rodolfo,
Don't bother including Frodo L. and Mark S. in the discussions, they
have left the lm-sensors project years ago.
On Thu, 10 Sep 2009 14:30:10 +0200, Rodolfo Giometti wrote:
> The file has been splitted up into two parts:
>
> * drivers/mfd/w83627hf.c - detects the chip and define proper
> platform devices into mfd support
>
> * drivers/hwmon/hwmon-w83627hf.c - implements the driver for hwmon
> functionality only
>
> The patch also fixes up some non reentrant code and some C-style issues.
>
> Signed-off-by: Rodolfo Giometti <giometti@linux.it>
> ---
> drivers/hwmon/Kconfig | 2 +-
> drivers/hwmon/Makefile | 2 +-
> drivers/hwmon/{w83627hf.c => hwmon-w83627hf.c} | 373 +++++-------------------
This name change will break all users of the driver. The sensors-detect
script points the user to "w83627hf" and typically writes this value to
an init script or configuration file. The w83627hf driver doesn't
auto-load (yet) so this is a requirement.
Assuming that the hwmon part depends on the MFD part, I'd rather keep
"w83627hf" as the hwmon part name, and name the new MFD part
"w83627hf-core" or similar. I agree it's not so nice but at least it
doesn't break compatibility.
> drivers/mfd/Kconfig | 14 +
> drivers/mfd/Makefile | 1 +
> drivers/mfd/w83627hf.c | 251 ++++++++++++++++
> include/linux/mfd/w83627hf.h | 68 +++++
> 7 files changed, 411 insertions(+), 300 deletions(-)
> rename drivers/hwmon/{w83627hf.c => hwmon-w83627hf.c} (85%)
> create mode 100644 drivers/mfd/w83627hf.c
> create mode 100644 include/linux/mfd/w83627hf.h
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-09-10 12:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 12:30 [lm-sensors] [PATCH] hwmon w83627hf: add mfd support Rodolfo Giometti
2009-09-10 12:56 ` Jean Delvare [this message]
2009-09-11 7:42 ` Rodolfo Giometti
2009-09-11 10:58 ` Samuel Ortiz
2009-09-11 15:07 ` Rodolfo Giometti
2009-09-15 11:38 ` Samuel Ortiz
2009-09-17 13:34 ` Jean Delvare
2009-09-17 13:51 ` Rodolfo Giometti
2009-09-17 13:57 ` Jean Delvare
2009-09-17 14:03 ` Rodolfo Giometti
2009-09-17 14:07 ` Jean Delvare
2009-09-17 14:34 ` Samuel Ortiz
2009-09-18 7:42 ` Jean Delvare
2009-09-18 8:01 ` Samuel Ortiz
2009-09-18 11:02 ` Rodolfo Giometti
2009-09-18 12:09 ` Rodolfo Giometti
2009-09-18 14:42 ` Samuel Ortiz
2009-09-18 14:49 ` Jean Delvare
2009-09-18 16:16 ` Jean Delvare
2009-09-20 23:48 ` Samuel Ortiz
2009-09-22 8:22 ` Rodolfo Giometti
2009-09-22 8:26 ` Rodolfo Giometti
2009-09-22 8:33 ` Rodolfo Giometti
2009-10-01 13:23 ` Jean Delvare
2009-10-01 13:53 ` Samuel Ortiz
2009-11-02 13:23 ` Jean Delvare
2009-11-03 8:17 ` Rodolfo Giometti
-- strict thread matches above, loose matches on Subject: below --
2010-02-10 12:18 Rodolfo Giometti
2010-02-27 10:58 ` Jean Delvare
2011-09-22 9:11 ` Rodolfo Giometti
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=20090910145609.200ee1f0@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.