From: Olof Johansson <olof@lixom.net>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Zhang Rui <rui.zhang@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
Linux-pm mailing list <linux-pm@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] Thermal: introduce INT3406 thermal driver
Date: Wed, 10 Dec 2014 18:22:58 -0800 [thread overview]
Message-ID: <CAOesGMjgCbDys-RXQ2SWOcO6rNkgkQ3ZWuqsMUVMzuicES3CFA@mail.gmail.com> (raw)
In-Reply-To: <5488FEAC.2010005@intel.com>
On Wed, Dec 10, 2014 at 6:17 PM, Aaron Lu <aaron.lu@intel.com> wrote:
> On 12/11/2014 10:15 AM, Olof Johansson wrote:
>> On Wed, Dec 10, 2014 at 5:02 PM, Aaron Lu <aaron.lu@intel.com> wrote:
>>> On Wed, Dec 10, 2014 at 11:53:25AM -0800, Olof Johansson wrote:
>>>> Hi,
>>>>
>>>> [+daniel vetter]
>>>>
>>>> On Mon, Dec 8, 2014 at 9:47 PM, Aaron Lu <aaron.lu@intel.com> wrote:
>>>>> INT3406 ACPI device object resembles an ACPI video output device, but its
>>>>> _BCM is said to be deprecated and should not be used. So we will make
>>>>> use of the raw interface to do the actual cooling. Due to this, the
>>>>> backlight core has some modifications. Also, to re-use some of the ACPI
>>>>> video module's code, one function has been exported.
>>>>>
>>>>> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
>>>>> Signed-off-by: Zhang Rui <rui.zhang@intel.com>
>>>>> ---
>>>>> v5:
>>>>> Add the missing file drivers/thermal/int340x_thermal/Kconfig
>>>>> Remove the assignment of .owner field from the device_driver structure
>>>>
>>>>
>>>> Did this patch show up in -next for the first time last night, or did
>>>> some other change break this?
>>>>
>>>> It causes a panic in i915 when booting Minnowboard Max for me.
>>>
>>> Sorry for the trouble, I'm looking at this now.
>>> Is there anything special about the Minnowboard Max? I'll try to
>>> reproduce the issue here locally with a typical Intel desktop.
>>
>> Another good question is why the code showed up in -next today. Code
>> going in for 3.19 is supposed to have been baking there already, and
>> it's too early to stage anything for 3.20.
>>
>> Zhang?
>>
>>> Is it the next/master branch?
>>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>
>> Yes. But I've confirmed that it happens with Zhang's next branch too
>> without the rest of linux-next.
>
> Can you please give me your kernel config file too?
http://arm-soc.lixom.net/minnowmax_defconfig
-Olof
next prev parent reply other threads:[~2014-12-11 2:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 5:47 [PATCH v5] Thermal: introduce INT3406 thermal driver Aaron Lu
2014-12-10 19:53 ` Olof Johansson
2014-12-11 1:02 ` Aaron Lu
2014-12-11 2:15 ` Olof Johansson
2014-12-11 2:17 ` Aaron Lu
2014-12-11 2:22 ` Olof Johansson [this message]
2014-12-11 2:37 ` Zhang Rui
2014-12-11 6:08 ` Aaron Lu
2014-12-11 6:10 ` Aaron Lu
2014-12-11 8:33 ` Zhang Rui
2014-12-11 8:38 ` [PATCH v6] " Aaron Lu
2014-12-12 18:18 ` Olof Johansson
2014-12-16 1:59 ` Aaron Lu
2014-12-22 3:09 ` Zhang Rui
2014-12-22 9:53 ` Lee Jones
2014-12-23 1:26 ` Aaron Lu
2014-12-29 6:03 ` Aaron Lu
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=CAOesGMjgCbDys-RXQ2SWOcO6rNkgkQ3ZWuqsMUVMzuicES3CFA@mail.gmail.com \
--to=olof@lixom.net \
--cc=aaron.lu@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sfr@canb.auug.org.au \
/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).