linux-kernel - Re: [PATCH] ARM: Exynos4: Bring exynos4-dt up to date

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:	Thu, 09 Feb 2012 10:24:32 +0100
From:	Karol Lewandowski <k.lewandowsk@...sung.com>
To:	kgene.kim@...sung.com
Cc:	thomas.abraham@...aro.org, m.szyprowski@...sung.com,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	kyungmin.park@...sung.com
Subject: Re: [PATCH] ARM: Exynos4: Bring exynos4-dt up to date

On 31.01.2012 17:47, Karol Lewandowski wrote:

> This commit brings exynos4-dt in line with recent changes to
> mach-exynos tree, specifically:
> 
>  - Fixes build break related to replacing plat/exynos4.h with common.h
>    in commit cc511b8d84d8 ("ARM: 7257/1: EXYNOS: introduce
>    arch/arm/mach-exynos/common.[ch]")


 
>  - Converts machine to use CONFIG_MULTI_IRQ_HANDLER as done for other
>    machines in commit 4e44d2cb95bd ("ARM: exynos4: convert to
>    CONFIG_MULTI_IRQ_HANDLER") converted all exynos boards but
>    exynos4-dt.c.


Minor correction - text from "converted all.." shall be deleted, like:

   - Converts machine to use CONFIG_MULTI_IRQ_HANDLER as done for other
     machines in commit 4e44d2cb95bd ("ARM: exynos4: convert to
     CONFIG_MULTI_IRQ_HANDLER")

(It's result of not proofreading it carefully enough after squashing all
the patches.)

I don't think such a change is worth sending patch again, but I would be
grateful if you could fix it while merging.

Thanks

-- 
Karol Lewandowski | Samsung Poland R&D Center | Linux/Platform


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