From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: exynos4: build is failing due to missing SZ_4K definition
Date: Fri, 07 Oct 2011 20:24:01 +0900 [thread overview]
Message-ID: <01f801cc84e3$9d5640e0$d802c2a0$%kim@samsung.com> (raw)
In-Reply-To: <1317938595-7007-1-git-send-email-angus.ainslie@linaro.org>
Angus Ainslie wrote:
>
> linux-next build is failing using the exynos4_defconfig. <asm/sizes.h>
needs to be
> for the SZ_4K definition
>
> Signed-off-by: Angus Ainslie <angus.ainslie@linaro.org>
> ---
> arch/arm/mach-exynos4/include/mach/map.h | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-exynos4/include/mach/map.h b/arch/arm/mach-
> exynos4/include/mach/map.h
> index 918a979..02d68f1 100644
> --- a/arch/arm/mach-exynos4/include/mach/map.h
> +++ b/arch/arm/mach-exynos4/include/mach/map.h
> @@ -13,6 +13,7 @@
> #ifndef __ASM_ARCH_MAP_H
> #define __ASM_ARCH_MAP_H __FILE__
>
> +#include <asm/sizes.h>
> #include <plat/map-base.h>
>
> /*
> --
> 1.7.4.1
Hi Angus,
I'm not sure why to add <asm/sizes.h> in mach/map.h is required now because
there was no adding SZ_ here between v3.1-rc1 and current HEAD in my -next.
Maybe if it is required, here is not proper place?......
Since I can't fetch linux-next from
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git, I need
some time. Let me check again with latest linux-next soon.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2011-10-07 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 22:03 [PATCH] arm: exynos4: build is failing due to missing SZ_4K definition Angus Ainslie
2011-10-07 11:24 ` Kukjin Kim [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01f801cc84e3$9d5640e0$d802c2a0$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).