From: Guenter Roeck <linux@roeck-us.net>
To: "Balac, Arun Saravanan" <ArunSaravanan.Balach@Dell.com>,
"jdelvare@suse.com" <jdelvare@suse.com>
Cc: "linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>
Subject: Re: [PATCH 0/5] hwmon: Add driver for MAX6620 Fan controller
Date: Tue, 6 Jul 2021 06:11:31 -0700 [thread overview]
Message-ID: <c058d3c0-2977-00cc-fba8-2eb81b28095a@roeck-us.net> (raw)
In-Reply-To: <MW2PR1901MB20287B190088EC2608094AF2A61B9@MW2PR1901MB2028.namprd19.prod.outlook.com>
On 7/6/21 6:01 AM, Balac, Arun Saravanan wrote:
> From: Arun Saravanan Balachandran <Arun_Saravanan_Balac@dell.com>
>
> Add driver for MAX6620 Fan controller
>
> Arun Saravanan Balachandran (2):
> Add attributes in MAX6620 driver to retrieve fan fault status
> Update MAX6620 driver as per linux code guidelines
>
> Cumulus Networks (2):
> Driver for MAX6620 Fan sensor
> MAX6620 fix rpm calculation accuracy
>
> Shuotian Cheng (1):
> Update MAX6620 driver to support newer kernel version
>
> drivers/hwmon/Kconfig | 10 +
> drivers/hwmon/Makefile | 1 +
> drivers/hwmon/max6620.c | 625 ++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 636 insertions(+)
> create mode 100644 drivers/hwmon/max6620.c
>
>
> base-commit: 303392fd5c160822bf778270b28ec5ea50cab2b4
>
Please squash all patches into one, and please use
devm_hwmon_device_register_with_info to register the hardware
monitoring device.
Also please follow the guidelines in
Documentation/hwmon/submitting-patches.rst.
Thanks,
Guenter
next prev parent reply other threads:[~2021-07-06 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 13:01 [PATCH 0/5] hwmon: Add driver for MAX6620 Fan controller Balac, Arun Saravanan
2021-07-06 13:11 ` Guenter Roeck [this message]
2021-07-26 7:47 ` Balac, Arun Saravanan
2021-07-26 13:42 ` Guenter Roeck
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=c058d3c0-2977-00cc-fba8-2eb81b28095a@roeck-us.net \
--to=linux@roeck-us.net \
--cc=ArunSaravanan.Balach@Dell.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).