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]
Date:	Fri, 20 Nov 2015 09:01:35 +0900
From:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
To:	Timo Sigurdsson <public_timo.s@...entcreek.de>, arnd@...db.de,
	javier@....samsung.com, kgene@...nel.org, linux@....linux.org.uk,
	olof@...om.net, geert+renesas@...der.be, lee.jones@...aro.org,
	sjoerd.simons@...labora.co.uk,
	alexandre.belloni@...e-electrons.com,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc:	maxime.ripard@...e-electrons.com, linux-sunxi@...glegroups.com,
	wens@...e.org
Subject: Re: [PATCH v2] ARM: sunxi: Re-enable SID driver in multi_v7_defconfig

On 20.11.2015 06:33, Timo Sigurdsson wrote:
> Commit 3d0b16a66c8a ("nvmem: sunxi: Move the SID driver to the nvmem
> framework") moved the the sunxi SID driver to a new framework, but left
> multi_v7_defconfig with the deprecated config symbol EEPROM_SUNXI_SID
> instead of the new symbol NVMEM_SUNXI_SID. Hence, re-enable the driver
> in multi_v7_defconfig.
> 
> Signed-off-by: Timo Sigurdsson <public_timo.s@...entcreek.de>
> ---
> Changes in v2:
> - Move the extra cleanup work for multi_v7_defconfig to a separate
>   patch (to be submitted at a later point to avoid conflicts with
>   another patch waiting to be merged)
> ---
>  arch/arm/configs/multi_v7_defconfig | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 

Fully satisfies my v1's comments:

Acked-by: Krzysztof Kozlowski <k.kozlowski@...sung.com>

Best regards,
Krzysztof

--
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