From: Mark Brown <broonie@kernel.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: linux-kernel@vger.kernel.org, edubezval@gmail.com,
rui.zhang@intel.com, Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms+renesas@verge.net.au>
Subject: Re: Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree
Date: Tue, 8 Mar 2016 09:22:25 +0700 [thread overview]
Message-ID: <20160308022225.GW18327@sirena.org.uk> (raw)
In-Reply-To: <56DD5DD2.9050101@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
On Mon, Mar 07, 2016 at 04:24:10PM +0530, Laxman Dewangan wrote:
> On Monday 07 March 2016 01:14 PM, Mark Brown wrote:
> >So that should be depends on THERMAL if THERMAL_OF
> depends on THERMAL && THERMAL_OF
THERMAL_OF hopefully can't be enabled without THERMAL.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-08 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 12:25 Mark Brown
2016-03-06 2:35 ` Mark Brown
2016-03-06 7:47 ` Laxman Dewangan
2016-03-06 11:35 ` Mark Brown
2016-03-07 6:36 ` Laxman Dewangan
2016-03-07 7:44 ` Mark Brown
2016-03-07 10:54 ` Laxman Dewangan
2016-03-08 2:22 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-13 9:59 [PATCH V3 2/2] regulator: max8973: add support for junction thermal warning Laxman Dewangan
2016-04-13 16:21 ` Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree Mark Brown
2016-04-13 17:01 ` Laxman Dewangan
2016-01-06 16:07 [PATCH V2] regulator: max8973: add support for junction thermal warning Laxman Dewangan
2016-01-06 18:12 ` Applied "regulator: max8973: add support for junction thermal warning" to the regulator tree Mark Brown
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=20160308022225.GW18327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=edubezval@gmail.com \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--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®