Re: [PATCH 6/9] power_supply: wm97xx_battery: use power_supply_get_drvdata

From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Kevin Hilman <khilman@kernel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Lee Jones <lee.jones@linaro.org>,
	Sebastian Reichel <sre@kernel.org>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Daniel Mack <daniel@zonque.org>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org, patches@opensource.wolfsonmicro.com,
	linux-pm <linux-pm@vger.kernel.org>,
	alsa-devel@alsa-project.org,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Stefan Agner <stefan@agner.ch>
Subject: Re: [PATCH 6/9] power_supply: wm97xx_battery: use power_supply_get_drvdata
Date: Tue, 24 Jan 2017 08:31:59 +0100	[thread overview]
Message-ID: <87h94odic0.fsf@belgarion.home> (raw)
In-Reply-To: <CAOi56cVk17w6C6msnT88c0Zh1OgLM=FbZAw32MzLRatjFraYhg@mail.gmail.com> (Kevin Hilman's message of "Mon, 23 Jan 2017 10:38:15 -0800")

Kevin Hilman <khilman@kernel.org> writes:

> Hello,
>
> On Wed, Oct 26, 2016 at 12:41 PM, Robert Jarzmik <robert.jarzmik@free.fr> wrote:
>> As the power supply framework provides a way to store and retrieve
>> private supply data, use it.
>>
>> In the process, change the platform data for wm97xx_battery from a
>> container of a single struct wm97xx_batt_pdata to the direct point to wm97xx_batt_pdata.
>>
>> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
>
> kernelci.org has been reporting that the tegra20-iris board has been
> failing in -next since next-20161123[1], and also in mainline
> v4.10-rc.  I finally took the time to bisect, and it pointed to this
> patch.  I verified that reverting $SUBJECT patch[2] on top of
> v4.10-rc5 fixes the problem.
>
> Kevin
>
> [1] https://kernelci.org/boot/id/5879a3fe59b5141534f6c3ac/
> [2] in mainline as commit: 6480af4915d6 power_supply: wm97xx_battery:
> use power_supply_get_drvdata

Hi Kevin,

There is a fix posted in here :
https://patchwork.kernel.org/patch/9499231/

I don't know if it's related, as I have no Oops signature nor any data to be
able to help further.

Cheers.

--
Robert