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: <9e448d3d42b4b3029e4b8993f2272e4c@milecki.pl>
Date:   Tue, 07 Mar 2023 10:41:15 +0100
From:   Rafał Miłecki <rafal@...ecki.pl>
To:     Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc:     Pavel Machek <pavel@....cz>,
        Florian Fainelli <f.fainelli@...il.com>,
        linux-leds@...r.kernel.org,
        William Zhang <william.zhang@...adcom.com>,
        kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] leds: bcm63138: refer to ARCH_BCMBCA instead of
 ARCH_BCM4908

On 2023-03-07 09:29, Lukas Bulwahn wrote:
> diff --git a/drivers/leds/blink/Kconfig b/drivers/leds/blink/Kconfig
> index 945c84286a4e..bdcb7377cd4e 100644
> --- a/drivers/leds/blink/Kconfig
> +++ b/drivers/leds/blink/Kconfig
> @@ -1,10 +1,10 @@
>  config LEDS_BCM63138
>  	tristate "LED Support for Broadcom BCM63138 SoC"
>  	depends on LEDS_CLASS
> -	depends on ARCH_BCM4908 || ARCH_BCM_5301X || BCM63XX || COMPILE_TEST
> +	depends on ARCH_BCMBCA || ARCH_BCM_5301X || BCM63XX || COMPILE_TEST
>  	depends on HAS_IOMEM
>  	depends on OF
> -	default ARCH_BCM4908
> +	default ARCH_BCMBCA
>  	help
>  	  This option enables support for LED controller that is part of
>  	  BCM63138 SoC. The same hardware block is known to be also used

William: do we want LEDS_BCM63138 default on all BCMBCA devices?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ