From: rentao.bupt@gmail.com
To: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, openbmc@lists.ozlabs.org, taoren@fb.com,
mikechoi@fb.com
Cc: Tao Ren <rentao.bupt@gmail.com>
Subject: [PATCH 0/2] hwmon: (max127) Add Maxim MAX127 hardware monitoring
Date: Mon, 16 Nov 2020 17:09:42 -0800 [thread overview]
Message-ID: <20201117010944.28457-1-rentao.bupt@gmail.com> (raw)
From: Tao Ren <rentao.bupt@gmail.com>
The patch series adds hardware monitoring driver for the Maxim MAX127
chip.
Patch #1 adds the max127 hardware monitoring driver, and patch #2 adds
documentation for the driver.
Tao Ren (2):
hwmon: (max127) Add Maxim MAX127 hardware monitoring driver
docs: hwmon: Document max127 driver
Documentation/hwmon/index.rst | 1 +
Documentation/hwmon/max127.rst | 43 +++++
drivers/hwmon/Kconfig | 9 ++
drivers/hwmon/Makefile | 1 +
drivers/hwmon/max127.c | 286 +++++++++++++++++++++++++++++++++
5 files changed, 340 insertions(+)
create mode 100644 Documentation/hwmon/max127.rst
create mode 100644 drivers/hwmon/max127.c
--
2.17.1
next reply other threads:[~2020-11-17 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 1:09 rentao.bupt [this message]
2020-11-17 1:09 ` [PATCH 1/2] hwmon: (max127) Add Maxim MAX127 hardware monitoring driver rentao.bupt
2020-11-17 5:13 ` Guenter Roeck
2020-11-18 1:55 ` Tao Ren
2020-11-17 1:09 ` [PATCH 2/2] docs: hwmon: Document max127 driver rentao.bupt
2020-11-17 5:15 ` 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=20201117010944.28457-1-rentao.bupt@gmail.com \
--to=rentao.bupt@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jdelvare@suse.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mikechoi@fb.com \
--cc=netdev@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=taoren@fb.com \
/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).