From: "Heiko Stübner" <heiko@sntech.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: linux@roeck-us.net, jdelvare@suse.com, kgene@kernel.org,
krzk@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
thierry.reding@gmail.com, jonathanh@nvidia.com,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: hwmon (pwm-fan) Remove dead "cooling-*-state" properties
Date: Tue, 19 Mar 2019 16:27:51 +0100 [thread overview]
Message-ID: <14253588.EKW5T2lhLl@diego> (raw)
In-Reply-To: <afde4ebd929821d63b5172c8e70e15f0725a4b49.1553006788.git.robin.murphy@arm.com>
Am Dienstag, 19. März 2019, 15:54:04 CET schrieb Robin Murphy:
> The old "cooling-{min,max}-state" properties for thermal bindings were
> ratified to "cooling-{min,max}-level" by commit eb168b70dea5 ("of:
> thermal: Fix inconsitency between cooling-*-state and cooling-*-level"),
> which were later removed entirely by commit e04907dbc259 ("dt-bindings:
> thermal: Remove "cooling-{min|max}-level" properties").
>
> The pwm-fan binding, however, was apparently in-flight in parallel with
> that ratification, and so managed to introduce an example of the old
> properties which escaped the scope of the later cleanup and has thus
> continued to be dutifully copied for new boards despite being useless.
> Clean up these remaining undocumented anachronisms to minimise any
> further confusion.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
>
> Presented as one big hwmon patch for simplicity, but the DT changes
> can quite easily be broken out by platform if maintainers prefer.
For the Rockchip-parts
Acked-by: Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2019-03-19 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 14:54 [PATCH] dt-bindings: hwmon (pwm-fan) Remove dead "cooling-*-state" properties Robin Murphy
2019-03-19 15:00 ` Guenter Roeck
2019-03-19 15:06 ` Krzysztof Kozlowski
2019-03-27 16:17 ` Robin Murphy
2019-03-19 15:14 ` Thierry Reding
2019-03-19 15:27 ` Heiko Stübner [this message]
2019-03-22 0:46 ` Shawn Guo
2019-03-31 6:40 ` Rob Herring
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=14253588.EKW5T2lhLl@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=jonathanh@nvidia.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robin.murphy@arm.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=thierry.reding@gmail.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).