From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: omap3: Include missing bandgap data for ti-soc-thermal driver
Date: Wed, 27 Jan 2016 10:24:48 -0800 [thread overview]
Message-ID: <20160127182447.GR19432@atomide.com> (raw)
In-Reply-To: <20160127181950.GB17794@earth>
* Sebastian Reichel <sre@kernel.org> [160127 10:20]:
> Hi,
>
> On Wed, Jan 27, 2016 at 08:09:46AM -0800, Tony Lindgren wrote:
> > * Pali Roh?r <pali.rohar@gmail.com> [160127 02:05]:
> > > On Thursday 21 January 2016 09:15:01 Tony Lindgren wrote:
> > > > * Pali Roh?r <pali.rohar@gmail.com> [160121 01:48]:
> > > > > On Saturday 26 December 2015 00:32:25 Pali Roh?r wrote:
> > > > > > Driver for omap3 with documentation is there since v4.4-rc1.
> > > > ...
> > > >
> > > > > PING! Who can take this patch?
> > > >
> > > > Sounds like /me, but after -rc1 when any possible regressions
> > > > are out of the way :)
> > >
> > > Great! Just to note that 4.5-rc1 is out.
> > >
> > > I just do not want to see this patch lost...
> >
> > So is this critical to have as a fix since it's thermal related?
>
> According to somebody from TI, who previously took part in the patch
> discussion, the thermal sensors of omap3 are to imprecise to be used
> for thermal decisions. The driver "just" informs userspace about the
> temperatures.
OK applying into omap-for-v4.6/dt then thanks.
Tony
prev parent reply other threads:[~2016-01-27 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 23:32 [PATCH] ARM: dts: omap3: Include missing bandgap data for ti-soc-thermal driver Pali Rohár
2015-12-26 18:50 ` Pavel Machek
2015-12-31 17:38 ` Eduardo Valentin
2016-01-05 11:30 ` Pali Rohár
2016-01-21 9:47 ` Pali Rohár
2016-01-21 17:15 ` Tony Lindgren
2016-01-27 10:04 ` Pali Rohár
2016-01-27 16:09 ` Tony Lindgren
2016-01-27 18:19 ` Sebastian Reichel
2016-01-27 18:24 ` Tony Lindgren [this message]
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=20160127182447.GR19432@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).