From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: Build broken on linus/master?
Date: Fri, 26 Oct 2012 14:29:28 +0530 [thread overview]
Message-ID: <508A50F0.2030308@ti.com> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433EBE9565@DBDE01.ent.ti.com>
On Friday 26 October 2012 01:18 PM, Bedia, Vaibhav wrote:
> Hi,
>
> Compiling the current linus/master (2ab3f29) using omap2plus_defconfig
> throws up the following error
>
> $make -j7 uImage
> CHK include/generated/uapi/linux/version.h
> CHK include/generated/utsrelease.h
> make[1]: `include/generated/mach-types.h' is up to date.
> CC arch/arm/kernel/asm-offsets.s
> In file included from include/linux/dma-mapping.h:76:0,
> from arch/arm/kernel/asm-offsets.c:15:
> /datalocal/kernel/arch/arm/include/asm/dma-mapping.h: In function 'dma_mapping_error':
> /datalocal/kernel/arch/arm/include/asm/dma-mapping.h:94:2: error: implicit declaration of function 'debug_dma_mapping_error'
> make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1
> make: *** [prepare0] Error 2
>
Looks like it might break build on all ARM machines. I just
noticed a patch adding debug_dma_mapping_error() for aarm64 arch.
Marek, Shuah,
Is kernel missing a patch which adds definition of
debug_dma_mapping_error() to linux/dma-debug.h ?
I can't seems to find this symbol in kernel grep.
Regards
Santosh
next prev parent reply other threads:[~2012-10-26 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 7:48 Build broken on linus/master? Bedia, Vaibhav
2012-10-26 8:59 ` Santosh Shilimkar [this message]
2012-10-26 10:02 ` Bedia, Vaibhav
2012-10-26 10:21 ` Santosh Shilimkar
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=508A50F0.2030308@ti.com \
--to=santosh.shilimkar@ti.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).