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] [day] [month] [year] [list]
Message-ID: <73451521-a4d3-d945-2c86-cceef4cc6781@broadcom.com>
Date:   Mon, 30 Dec 2019 11:33:04 -0800
From:   Florian Fainelli <florian.fainelli@...adcom.com>
To:     Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
        Florian Fainelli <f.fainelli@...il.com>,
        Thierry Reding <thierry.reding@...il.com>,
        Krzysztof Kozlowski <krzk@...nel.org>
Cc:     linux-kernel@...r.kernel.org,
        bcm-kernel-feedback-list@...adcom.com, wahrenst@....net,
        "open list:PWM SUBSYSTEM" <linux-pwm@...r.kernel.org>
Subject: Re: [PATCH] pwm: bcm2835: Allow building for ARCH_BRCMSTB

On 12/9/19 10:52 PM, Uwe Kleine-König wrote:
> On Mon, Dec 09, 2019 at 03:25:03PM -0800, Florian Fainelli wrote:
>> BCM7211 is supported using ARCH_BRCMSTB and uses this PWM controller
>> driver, make it possible to build it.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
>> ---
>>  drivers/pwm/Kconfig | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig
>> index bd21655c37a6..0bb8a40c8d6c 100644
>> --- a/drivers/pwm/Kconfig
>> +++ b/drivers/pwm/Kconfig
>> @@ -100,7 +100,7 @@ config PWM_BCM_KONA
>>  
>>  config PWM_BCM2835
>>  	tristate "BCM2835 PWM support"
>> -	depends on ARCH_BCM2835
>> +	depends on ARCH_BCM2835 || ARCH_BRCMSTB
> 
> It would be nice to allow this driver to be compiled with COMPILE_TEST,
> too. But also without this:
> 
> Acked-by: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>

Krysztof just submitted a patch doing that [1], which will conflict with
this one. Thierry would you be able to resolve that conflict while applying?

[1]:
https://lore.kernel.org/linux-arm-kernel/20191230172113.17222-2-krzk@kernel.org/
-- 
Florian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ