From: Krzysztof Adamski <krzysztof.adamski@nokia.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh+dt@kernel.org>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 3/9] hwmon: (tmp421) support disabling channels from DT
Date: Sun, 17 Oct 2021 02:00:32 +0200 [thread overview]
Message-ID: <YWtnoC5s/W8/st41@localhost.localdomain> (raw)
In-Reply-To: <20211015224741.GA1484653@roeck-us.net>
Dnia Fri, Oct 15, 2021 at 03:47:41PM -0700, Guenter Roeck napisał(a):
>On Thu, Oct 14, 2021 at 03:01:09PM +0200, Krzysztof Adamski wrote:
>> The previous patch introduced per channel subnodes in DT that let us
>> specify some channel specific properties. This built a ground for easily
>> disabling individual channels of the sensor that may not be connected to
>> any external diode and thus are not returning any meaningful data.
>>
>> This patch adds support for parsing the "status" property of channels DT
>> subnodes and makes sure the -ENODATA is returned when disabled channels
>> value is read.
>>
>> Signed-off-by: Krzysztof Adamski <krzysztof.adamski@nokia.com>
>
>Same problem as with patch 2/9. Any idea what happened ?
>
>Anyway, applied after fixing it up.
Thank you and sorry for the trouble. It isn't trivial to send patches
via our enterprise mail platform and this time I had to contrive more
than usually. I did use mutt, as I usually do, but had to run it from
different machine. Even though I did use the same config, the mutt
version was different and EDITOR might have been configured differently,
so maybe that created a problem? Or it was the Exchange server which
mangled my patches? I don't know now but I will watch out for that,
thank you for the heads up on that.
Best regards,
Krzysztof Adamski
next prev parent reply other threads:[~2021-10-17 0:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 13:00 [PATCH v5 0/9] Add per channel properies support in tmp421 Krzysztof Adamski
2021-10-14 13:00 ` [PATCH v5 1/9] dt-bindings: hwmon: add missing tmp421 binding Krzysztof Adamski
2021-10-14 16:31 ` Rob Herring
2021-10-15 22:29 ` Guenter Roeck
2021-10-14 13:00 ` [PATCH v5 2/9] hwmon: (tmp421) add support for defining labels from DT Krzysztof Adamski
2021-10-15 22:45 ` Guenter Roeck
2021-10-14 13:01 ` [PATCH v5 3/9] hwmon: (tmp421) support disabling channels " Krzysztof Adamski
2021-10-15 22:47 ` Guenter Roeck
2021-10-17 0:00 ` Krzysztof Adamski [this message]
2021-10-14 13:01 ` [PATCH v5 4/9] hwmon: (tmp421) support specifying n-factor via DT Krzysztof Adamski
2021-10-15 22:49 ` Guenter Roeck
2021-10-14 13:09 ` [PATCH v5 5/9] hwmon: (tmp421) really disable channels Krzysztof Adamski
2021-10-15 22:53 ` Guenter Roeck
2021-10-14 13:09 ` [PATCH v5 6/9] hwmon: (tmp421) support HWMON_T_ENABLE Krzysztof Adamski
2021-10-15 22:53 ` Guenter Roeck
2021-10-14 13:10 ` [PATCH v5 7/9] hwmon: (tmp421) update documentation Krzysztof Adamski
2021-10-15 22:54 ` Guenter Roeck
2021-10-14 13:11 ` [PATCH v5 8/9] hwmon: (tmp421) ignore non-channel related DT nodes Krzysztof Adamski
2021-10-15 22:56 ` Guenter Roeck
2021-10-14 13:11 ` [PATCH v5 9/9] dt-bindings: hwmon: allow specifying channels for tmp421 Krzysztof Adamski
2021-10-14 16:31 ` Rob Herring
2021-10-15 22:57 ` 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=YWtnoC5s/W8/st41@localhost.localdomain \
--to=krzysztof.adamski@nokia.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--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