From: Andrew Lunn <andrew@lunn.ch>
To: rentao.bupt@gmail.com
Cc: 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
Subject: Re: [PATCH v2 0/2] hwmon: (max127) Add Maxim MAX127 hardware monitoring
Date: Thu, 19 Nov 2020 00:27:19 +0100 [thread overview]
Message-ID: <20201118232719.GI1853236@lunn.ch> (raw)
In-Reply-To: <20201118230929.18147-1-rentao.bupt@gmail.com>
On Wed, Nov 18, 2020 at 03:09:27PM -0800, rentao.bupt@gmail.com wrote:
> From: Tao Ren <rentao.bupt@gmail.com>
>
> The patch series adds hardware monitoring driver for the Maxim MAX127
> chip.
Hi Tao
Why are using sending a hwmon driver to the networking mailing list?
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: rentao.bupt@gmail.com
Cc: linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jonathan Corbet <corbet@lwn.net>,
netdev@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-doc@vger.kernel.org,
John Fastabend <john.fastabend@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
linux-kernel@vger.kernel.org, taoren@fb.com,
Jakub Kicinski <kuba@kernel.org>,
bpf@vger.kernel.org, mikechoi@fb.com,
"David S . Miller" <davem@davemloft.net>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v2 0/2] hwmon: (max127) Add Maxim MAX127 hardware monitoring
Date: Thu, 19 Nov 2020 00:27:19 +0100 [thread overview]
Message-ID: <20201118232719.GI1853236@lunn.ch> (raw)
In-Reply-To: <20201118230929.18147-1-rentao.bupt@gmail.com>
On Wed, Nov 18, 2020 at 03:09:27PM -0800, rentao.bupt@gmail.com wrote:
> From: Tao Ren <rentao.bupt@gmail.com>
>
> The patch series adds hardware monitoring driver for the Maxim MAX127
> chip.
Hi Tao
Why are using sending a hwmon driver to the networking mailing list?
Andrew
next prev parent reply other threads:[~2020-11-18 23:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 23:09 [PATCH v2 0/2] hwmon: (max127) Add Maxim MAX127 hardware monitoring rentao.bupt
2020-11-18 23:09 ` [PATCH v2 1/2] hwmon: (max127) Add Maxim MAX127 hardware monitoring driver rentao.bupt
2020-11-18 23:09 ` [PATCH v2 2/2] docs: hwmon: Document max127 driver rentao.bupt
2020-11-18 23:27 ` Andrew Lunn [this message]
2020-11-18 23:27 ` [PATCH v2 0/2] hwmon: (max127) Add Maxim MAX127 hardware monitoring Andrew Lunn
2020-11-18 23:42 ` Tao Ren
2020-11-18 23:42 ` Tao Ren
2020-11-19 1:01 ` Guenter Roeck
2020-11-19 1:01 ` Guenter Roeck
2020-11-19 1:26 ` Guenter Roeck
2020-11-19 1:26 ` Guenter Roeck
2020-11-19 7:22 ` Tao Ren
2020-11-19 7:22 ` Tao Ren
2020-11-19 15:46 ` Jakub Kicinski
2020-11-19 15:46 ` Jakub Kicinski
2020-11-19 16:35 ` XDP maintainer match (Was [PATCH v2 0/2] hwmon: (max127) Add Maxim MAX127 hardware monitoring) Jesper Dangaard Brouer
2020-11-19 16:35 ` Jesper Dangaard Brouer
2020-11-19 17:09 ` Joe Perches
2020-11-19 17:09 ` Joe Perches
2020-11-19 17:59 ` Jakub Kicinski
2020-11-19 17:59 ` Jakub Kicinski
2020-11-19 20:41 ` Jesper Dangaard Brouer
2020-11-19 20:41 ` Jesper Dangaard Brouer
2020-11-19 16:36 ` [PATCH v2 0/2] hwmon: (max127) Add Maxim MAX127 hardware monitoring Alexei Starovoitov
2020-11-19 16:36 ` Alexei Starovoitov
2020-11-19 1:28 ` Andrew Lunn
2020-11-19 1:28 ` Andrew Lunn
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=20201118232719.GI1853236@lunn.ch \
--to=andrew@lunn.ch \
--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=rentao.bupt@gmail.com \
--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 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.