linux-kernel - Re: [GIT PULL] ARM: EXYNOS: dts: DTS fixes for 4.1, second try

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: <55529F1B.3050703@samsung.com>
Date:	Wed, 13 May 2015 09:47:23 +0900
From:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
To:	Kukjin Kim <kgene@...nel.org>
Cc:	linux-samsung-soc@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
	linux-kernel@...r.kernel.org, Olof Johansson <olof@...om.net>,
	Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [GIT PULL] ARM: EXYNOS: dts: DTS fixes for 4.1, second try

On 13.05.2015 03:27, Kukjin Kim wrote:
> On 05/11/15 12:10, Krzysztof Kozlowski wrote:
>> Dear Kukjin,
>>
>> This groups one fix missed in your last pull requst. This fixes suspend
>> on Peach boards related to Marvell mwifiex driver. The driver was
>> enabled for Exynos defconfig during merge window so currently
>> the suspend on these boards on this config fails.
>>
> Yes, you're right. Only exynos5250-snow related patch has been fixed
> before and this should be sent to upstream together. I've applied this
> into samsung-fixes-2 with your signed-off-by.
> 
> Note this will be sent to arm-soc before a couple of days of -rc4 with
> your other fix for suspend on exynos4.

Great, thank you!

What about the patches for next release (v4.2 or v4.3)? Do you have any
comments on them? These are mostly small improvements except one: the
coupled cpuidle driver for Exynos3250.

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/