On 03/06/12 10:55, Olof Johansson wrote:
Hi,
On Tue, Feb 21, 2012 at 2:35 AM, Kukjin Kim<kgene.kim@xxxxxxxxxxx> wrote:
Yes, as you said, it brakes single zImage for EXYNOS4 + EXYNOS5
(mach-exynos). So I'm working on regarding resource for EXYNOS SoCs and I
think, it can resolve the problem you said before v3.4 merge window.
If any updates, let you know.
Just a friendly reminder; the time is close to running out for staging
new code for 3.4.
Hi Olof,
Thanks for your kindly reminder but I couldn't finish it yet because it
is required to touch most of samsung stuff, and it's a big change.
Frankly, I need more time...
So how about sending current exynos5 stuff for now and then sorting out
single kernel for exynos4 and exynos5 next time? Actually, this exynos5
arch part is _really_ needed for developing/contribution of drivers on
exynos5.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@xxxxxxxxxxx>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
