From: "Matwey V. Kornilov" <matwey@sai.msu.ru>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
"Matwey V. Kornilov" <matwey@sai.msu.ru>
Subject: [PATCH v4 0/4] hwmon: lm75: Handle broken device nodes gracefully
Date: Sat, 6 Feb 2021 12:51:17 +0300 [thread overview]
Message-ID: <20210206095121.20625-1-matwey@sai.msu.ru> (raw)
In-Reply-To: <2588ea5c-630e-6509-689d-4c8fea358e9b@roeck-us.net>
This series is to fix a logical issue in lm75 driver.
The actual fix is in the last patch.
Other patches are present in order not to break existing users.
Matwey V. Kornilov (4):
hwmon: lm75: Add lm75 to of_match list
hwmon: lm75: Add nxp,lm75a to of_match list
hwmon: lm75: Add ti,lm75 to of_match list
hwmon: lm75: Handle broken device nodes gracefully
.../devicetree/bindings/hwmon/lm75.yaml | 3 ++
drivers/hwmon/lm75.c | 32 +++++++++++++++++--
2 files changed, 32 insertions(+), 3 deletions(-)
--
2.26.2
next prev parent reply other threads:[~2021-02-06 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 10:38 [PATCH 1/2] hwmon: lm75: Add NXP LM75A to of_match list Matwey V. Kornilov
2021-01-30 10:38 ` [PATCH 2/2] hwmon: lm75: Add another name for NXP LM75B " Matwey V. Kornilov
2021-01-30 15:41 ` [PATCH 1/2] hwmon: lm75: Add NXP LM75A " Guenter Roeck
[not found] ` <CAJs94EbBAK1LAZt4pfbzbUCxJtRo8kTAxdaN=y_gRbuvX0rz8Q@mail.gmail.com>
2021-02-03 19:57 ` Guenter Roeck
2021-02-06 9:51 ` Matwey V. Kornilov [this message]
2021-02-06 9:51 ` [PATCH v4 1/4] hwmon: lm75: Add lm75 " Matwey V. Kornilov
2021-02-06 16:46 ` Guenter Roeck
2021-02-10 19:47 ` Rob Herring
2021-02-06 9:51 ` [PATCH v4 2/4] hwmon: lm75: Add nxp,lm75a " Matwey V. Kornilov
2021-02-06 16:48 ` Guenter Roeck
2021-02-06 16:54 ` Guenter Roeck
2021-02-06 9:51 ` [PATCH v4 3/4] hwmon: lm75: Add ti,lm75 " Matwey V. Kornilov
2021-02-06 16:54 ` Guenter Roeck
2021-02-06 9:51 ` [PATCH v4 4/4] hwmon: lm75: Handle broken device nodes gracefully Matwey V. Kornilov
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=20210206095121.20625-1-matwey@sai.msu.ru \
--to=matwey@sai.msu.ru \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@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).