On Wed, Jun 8, 2016 at 11:44 PM, Florian Fainelli wrote:
> drivers/pinctrl/bcm/Makefile properly builds individual drivers based on
> their respective Kconfig symbols. ARCH_BCM is currently a menuconfig
> option from arch/arm/mach-bcm/Kconfig, which is fine, but prevents
On Wed, Jun 8, 2016 at 11:44 PM, Florian Fainelli wrote:
> drivers/pinctrl/bcm/Makefile properly builds individual drivers based on
> their respective Kconfig symbols. ARCH_BCM is currently a menuconfig
> option from arch/arm/mach-bcm/Kconfig, which is fine, but prevents ARM64
> platforms which
Looks good.
On 16-06-08 02:44 PM, Florian Fainelli wrote:
drivers/pinctrl/bcm/Makefile properly builds individual drivers based on
their respective Kconfig symbols. ARCH_BCM is currently a menuconfig
option from arch/arm/mach-bcm/Kconfig, which is fine, but prevents ARM64
platforms which do not
Looks good.
On 16-06-08 02:44 PM, Florian Fainelli wrote:
drivers/pinctrl/bcm/Makefile properly builds individual drivers based on
their respective Kconfig symbols. ARCH_BCM is currently a menuconfig
option from arch/arm/mach-bcm/Kconfig, which is fine, but prevents ARM64
platforms which do not
drivers/pinctrl/bcm/Makefile properly builds individual drivers based on
their respective Kconfig symbols. ARCH_BCM is currently a menuconfig
option from arch/arm/mach-bcm/Kconfig, which is fine, but prevents ARM64
platforms which do not have such menuconfig option from building their
pinctrl
drivers/pinctrl/bcm/Makefile properly builds individual drivers based on
their respective Kconfig symbols. ARCH_BCM is currently a menuconfig
option from arch/arm/mach-bcm/Kconfig, which is fine, but prevents ARM64
platforms which do not have such menuconfig option from building their
pinctrl
6 matches
Mail list logo