From: Marek Szyprowski <m.szyprowski@samsung•com>
To: 'Paul Gortmaker' <paul.gortmaker@windriver•com>
Cc: kyungmin.park@samsung•com, linux-arm-kernel@lists•infradead.org,
linux-next@vger•kernel.org
Subject: RE: commit "ARM: dma-mapping: remove custom consistent dma region"
Date: Fri, 29 Jun 2012 07:22:33 +0200 [thread overview]
Message-ID: <000401cd55b7$327a1490$976e3db0$%szyprowski@samsung.com> (raw)
In-Reply-To: <20120627194604.GA9445@windriver.com>
Hi Paul,
On Wednesday, June 27, 2012 9:46 PM Paul Gortmaker wrote:
> This commit in linux-next:
>
> commit feb930cb9beb75cbe1d1e798870599c3aa1b93ec
> Author: Marek Szyprowski <m.szyprowski@samsung•com>
> Date: Fri Jun 8 12:08:32 2012 +0200
>
> ARM: dma-mapping: remove custom consistent dma region
>
> seems to break the at91x40_defconfig (according to git bisect).
>
> CC arch/arm/mm/dma-mapping.o
> arch/arm/mm/dma-mapping.c: In function '__dma_alloc':
> arch/arm/mm/dma-mapping.c:575: error: macro "__alloc_from_pool" requires 4 arguments, but only
> 2 given
> arch/arm/mm/dma-mapping.c:575: error: '__alloc_from_pool' undeclared (first use in this
> function)
> arch/arm/mm/dma-mapping.c:575: error: (Each undeclared identifier is reported only once
> arch/arm/mm/dma-mapping.c:575: error: for each function it appears in.)
> make[2]: *** [arch/arm/mm/dma-mapping.o] Error 1
> make[1]: *** [arch/arm/mm/dma-mapping.o] Error 2
>
> See http://kisskb.ellerman.id.au/kisskb/buildresult/6596769/ for a full log.
>
> Please have a look when you get a chance.
Thanks for the report! I've added a fix to my dma-mapping-next branch, the issue should go
away with the next update of linus-next tree.
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
prev parent reply other threads:[~2012-06-29 5:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 19:46 commit "ARM: dma-mapping: remove custom consistent dma region" Paul Gortmaker
2012-06-29 5:22 ` Marek Szyprowski [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='000401cd55b7$327a1490$976e3db0$%szyprowski@samsung.com' \
--to=m.szyprowski@samsung$(echo .)com \
--cc=kyungmin.park@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.gortmaker@windriver$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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