linux-kernel - Re: [PATCH 0/2] EXYNOS4_DT fixes for 3.3-rc1+ kernels

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: <CAJuYYwQepKi+TG1tOaZ=X9WEi3cwbwsoofuZBSqSiBb4LA_YoA@mail.gmail.com>
Date:	Tue, 31 Jan 2012 20:18:05 +0530
From:	Thomas Abraham <thomas.abraham@...aro.org>
To:	Karol Lewandowski <k.lewandowsk@...sung.com>
Cc:	m.szyprowski@...sung.com, linux-samsung-soc@...r.kernel.org,
	marc.zyngier@....com, linux-kernel@...r.kernel.org,
	kgene.kim@...sung.com, kyungmin.park@...sung.com
Subject: Re: [PATCH 0/2] EXYNOS4_DT fixes for 3.3-rc1+ kernels

Hi Karol,

On 31 January 2012 16:06, Karol Lewandowski <k.lewandowsk@...sung.com> wrote:
> Device Tree-based Exynos4 machine prepared by Thomas Abraham and
> included in 3.3-rc1 hasn't been adjusted to changes that have happened
> to mach-exynos during 3.3 merge window.
>
> Following patch series fixes one build and one boot error making it
> possible to boot system with SMP disabled.
>
> SMP support is still broken for unknown reason, though.
>
> [ To use it it's also required to cherry-pick "ARM: EXYNOS: fix
>  non-SMP builds for EXYNOS4" already found in kgene's
>  linux-samsung.git (branch v3.3-samsung-fixes-2) ]
>
>
> Karol Lewandowski (2):
>  ARM: Exynos4: Make exynos4-dt compile again
>  ARM: Exynos4: Convert exynos4-dt to CONFIG_MULTI_IRQ_HANDLER
>
>  arch/arm/mach-exynos/mach-exynos4-dt.c |    7 +++++--
>  1 files changed, 5 insertions(+), 2 deletions(-)

Thanks for these patches and identifying the issue.

Regards,
Thomas.

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