From: Laxman Dewangan <ldewangan@nvidia.com>
To: <edubezval@gmail.com>, <rui.zhang@intel.com>, <corbet@lwn.net>
Cc: <rklein@nvidia.com>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH 2/3] thermal: Add devm_thermal_zone_of_sensor_register() in managed devices list
Date: Fri, 4 Mar 2016 19:10:09 +0530 [thread overview]
Message-ID: <1457098810-11964-3-git-send-email-ldewangan@nvidia.com> (raw)
In-Reply-To: <1457098810-11964-1-git-send-email-ldewangan@nvidia.com>
thermal_zone_of_sensor_register() and thermal_zone_of_sensor_unregister()
gained their devm_ wrappers. Add these APIs in the list of managed devices.
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
Documentation/driver-model/devres.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/driver-model/devres.txt b/Documentation/driver-model/devres.txt
index 5930d9a..dd7ce58 100644
--- a/Documentation/driver-model/devres.txt
+++ b/Documentation/driver-model/devres.txt
@@ -342,6 +342,10 @@ SLAVE DMA ENGINE
SPI
devm_spi_register_master()
+THERMAL
+ devm_thermal_zone_of_sensor_register()
+ devm_thermal_zone_of_sensor_unregister()
+
WATCHDOG
devm_watchdog_register_device()
devm_watchdog_unregister_device()
--
2.1.4
next prev parent reply other threads:[~2016-03-04 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 13:40 [PATCH 0/3] thermal: add devm_ version of thermal_zone register and driver for max77620 Laxman Dewangan
2016-03-04 13:40 ` [PATCH 1/3] thermal: of-thermal: Add devm version of thermal_zone_of_sensor_register Laxman Dewangan
2016-03-08 21:29 ` Eduardo Valentin
2016-03-09 12:10 ` Laxman Dewangan
2016-03-04 13:40 ` Laxman Dewangan [this message]
2016-03-04 13:40 ` [PATCH 3/3] thermal: max77620: Add thermal driver for reporting junction temp Laxman Dewangan
2016-03-04 14:04 ` Laxman Dewangan
2016-03-08 21:24 ` Eduardo Valentin
2016-03-09 12:34 ` Laxman Dewangan
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=1457098810-11964-3-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=corbet@lwn.net \
--cc=edubezval@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rklein@nvidia.com \
--cc=rui.zhang@intel.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
all inboxes | Powered by JetHome®