linux-kernel - Re: [GIT PULL 2/2] bcm2835-drivers-next-2019-03-04

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <87ef7h3wi9.fsf@anholt.net>
Date:   Fri, 08 Mar 2019 13:07:58 -0800
From:   Eric Anholt <eric@...olt.net>
To:     Florian Fainelli <f.fainelli@...il.com>,
        Florian Fainelli <f.fainelli@...il.com>
Cc:     linux-rpi-kernel@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Stefan Wahren <stefan.wahren@...e.com>,
        bcm-kernel-feedback-list@...adcom.com
Subject: Re: [GIT PULL 2/2] bcm2835-drivers-next-2019-03-04

Florian Fainelli <f.fainelli@...il.com> writes:

> On 3/4/19 4:02 PM, Eric Anholt wrote:
>> The following changes since commit e1dc2b2e1bef7237fd8fc055fe1ec2a6ff001f91:
>> 
>>   ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware. (2019-02-01 10:34:32 +0100)
>> 
>> are available in the Git repository at:
>> 
>>   git://github.com/anholt/linux tags/bcm2835-drivers-next-2019-03-04
>> 
>> for you to fetch changes up to 4deabfae643d8852c643664d9088a647abfaa5d0:
>> 
>>   soc: bcm: bcm2835-pm: Fix error paths of initialization. (2019-03-04 15:33:14 -0800)
>> 
>> ----------------------------------------------------------------
>> This pull request brings in two fixes for the new native bcm2835 power
>> domains driver.
>> 
>> ----------------------------------------------------------------
>
> Looks like Stefan found an arm64 build configuration that failed linking
> with the driver, do you want to add an additional fix to this pull
> request that addresses that?

Took a look at it now, sent a fix.

Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)