From: Guenter Roeck <linux@roeck-us.net>
To: baneric926@gmail.com, jdelvare@suse.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
corbet@lwn.net
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
kcfeng0@nuvoton.com, kwliu@nuvoton.com, openbmc@lists.ozlabs.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
DELPHINE_CHIU@wiwynn.com
Subject: Re: [PATCH v1 0/2] hwmon: Driver for Nuvoton NCT736X
Date: Sun, 3 Dec 2023 23:04:53 -0800 [thread overview]
Message-ID: <4d978188-b924-4f43-a619-fb5307828440@roeck-us.net> (raw)
In-Reply-To: <20231204055650.788388-1-kcfeng0@nuvoton.com>
On 12/3/23 21:56, baneric926@gmail.com wrote:
> From: Ban Feng <baneric926@gmail.com>
>
> NCT736X is an I2C based hardware monitoring chip from Nuvoton.
>
No, it isn't. Such a chip does not exist. The chips are apparently
NCT7362Y and NCT7363Y. No wildcards in filenames, variables, etc.,
please. Pick one name (nct7362y) instead and reference both chips
where appropriate.
Guenter
next parent reply other threads:[~2023-12-04 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231204055650.788388-1-kcfeng0@nuvoton.com>
2023-12-04 7:04 ` Guenter Roeck [this message]
[not found] ` <20231204055650.788388-3-kcfeng0@nuvoton.com>
2023-12-04 7:06 ` [PATCH v1 2/2] hwmon: Driver for Nuvoton NCT736X Guenter Roeck
2023-12-05 11:04 ` kernel test robot
2023-12-05 14:14 ` kernel test robot
2023-12-07 5:41 ` Dan Carpenter
[not found] ` <20231204055650.788388-2-kcfeng0@nuvoton.com>
[not found] ` <94607c47-9824-4e2c-8f22-99ca2e088b27@linaro.org>
[not found] ` <CALz278ZbjcbjUmFKv4B20DPDW33KPW-nZn4if3qTLjYKZZmWWw@mail.gmail.com>
[not found] ` <4770f744-2309-4de0-8aaf-a221f69c08b7@linaro.org>
2023-12-08 3:05 ` [PATCH v1 1/2] dt-bindings: hwmon: Add nct736x bindings Ban Feng
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=4d978188-b924-4f43-a619-fb5307828440@roeck-us.net \
--to=linux@roeck-us.net \
--cc=DELPHINE_CHIU@wiwynn.com \
--cc=baneric926@gmail.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=kcfeng0@nuvoton.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kwliu@nuvoton.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@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 read-only IMAP folder(s) and NNTP newsgroup(s).