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: <546652F3.8050809@gmail.com>
Date:	Fri, 14 Nov 2014 20:07:31 +0100
From:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To:	Antoine Tenart <antoine.tenart@...e-electrons.com>
CC:	Arnd Bergmann <arnd@...db.de>, Peter.Chen@...escale.com,
	balbi@...com, p.zabel@...gutronix.de,
	alexandre.belloni@...e-electrons.com,
	thomas.petazzoni@...e-electrons.com, zmxu@...vell.com,
	jszhang@...vell.com, linux-arm-kernel@...ts.infradead.org,
	linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 03/13] ARM: Berlin: select the reset controller

On 14.11.2014 18:28, Antoine Tenart wrote:
> Sebastian,
>
> On Fri, Nov 14, 2014 at 04:36:50PM +0100, Sebastian Hesselbarth wrote:
>> On 11/14/2014 04:33 PM, Arnd Bergmann wrote:
>>> On Friday 14 November 2014 16:25:53 Antoine Tenart wrote:
>>>>   menuconfig ARCH_BERLIN
>>>>          bool "Marvell Berlin SoCs" if ARCH_MULTI_V7
>>>> +       select ARCH_HAS_RESET_CONTROLLER
>>>>          select ARCH_REQUIRE_GPIOLIB
>>>>          select ARM_GIC
>>>>          select GENERIC_IRQ_CHIP
>>>>          select DW_APB_ICTL
>>>>          select DW_APB_TIMER_OF
>>>>          select PINCTRL
>>>> +       select RESET_CONTROLLER
>>>
>>> RESET_CONTROLLER is meant to be user-selectable, don't add a 'select' here,
>>> but instead make the driver 'depends on RESET_CONTROLLER'.
>>
>> It already went into arm-soc for v3.19 - ergo, we need an extra
>> patch for removing the current 'select'.
>
> Do you want me to send the extra patch fixing this issue?

Yes, please. The patch in question is already in a tagged, stabled,
and pulled branch - so there is nothing I can do about it.

You can just send it as an independent patch, I'll pick it up quickly.

Sebastian

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ