lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 24 Jan 2017 08:31:59 +0100
From:   Robert Jarzmik <>
To:     Kevin Hilman <>
Cc:     Dmitry Torokhov <>,
        Lee Jones <>,
        Sebastian Reichel <>,
        Jaroslav Kysela <>,
        Takashi Iwai <>, Daniel Mack <>,
        Haojian Zhuang <>,
        Liam Girdwood <>,
        Mark Brown <>,
        lkml <>,,,
        linux-pm <>,,
        linux-arm-kernel <>,
        Stefan Agner <>
Subject: Re: [PATCH 6/9] power_supply: wm97xx_battery: use power_supply_get_drvdata

Kevin Hilman <> writes:

> Hello,
> On Wed, Oct 26, 2016 at 12:41 PM, Robert Jarzmik <> 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 <>
> 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]
> [2] in mainline as commit: 6480af4915d6 power_supply: wm97xx_battery:
> use power_supply_get_drvdata

Hi Kevin,

There is a fix posted in here :

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



Powered by blists - more mailing lists