From: Laura Abbott <lauraa@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Guenter Roeck <linux@roeck-us.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 27
Date: Wed, 27 Aug 2014 17:56:13 -0700 [thread overview]
Message-ID: <53FE7E2D.9060408@codeaurora.org> (raw)
In-Reply-To: <20140828104830.4447c5e5@canb.auug.org.au>
On 8/27/2014 5:48 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 27 Aug 2014 16:58:09 -0700 Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> I see a large number of build failures with this kernel.
>>
>> drivers/base/dma-mapping.c: In function 'dma_common_contiguous_remap':
>> drivers/base/dma-mapping.c:294:2: error: implicit declaration of function
>> 'dma_common_pages_remap' [-Werror=implicit-function-declaration]
>> drivers/base/dma-mapping.c:294:6: warning: assignment makes pointer from integer
>> without a cast [enabled by default]
>> drivers/base/dma-mapping.c: At top level:
>> drivers/base/dma-mapping.c:305:7: error: conflicting types for
>> 'dma_common_pages_remap'
>> drivers/base/dma-mapping.c:294:8: note: previous implicit declaration of
>> 'dma_common_pages_remap' was here
>> cc1: some warnings being treated as errors
>> make[2]: *** [drivers/base/dma-mapping.o] Error 1
>
> Caused by commit fa44abcad042 ("common: dma-mapping: introduce common
> remapping functions") from the akpm-current tree. I will attempt to
> revert that commit today, but I may need to also revert the following 2
> commits as well:
>
> arm: use genalloc for the atomic pool
> arm64: add atomic pool for non-coherent and CMA allocations
>
> though I am not sure. Hopefully someone will let me know in the next
> few hours ...
>
I sent fixes for this to Andrew yesterday, did those not get picked up
or fix the problem?
Thanks,
Laura
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-08-28 0:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 6:10 linux-next: Tree for Aug 27 Stephen Rothwell
2014-08-27 23:58 ` Guenter Roeck
2014-08-28 0:48 ` Stephen Rothwell
2014-08-28 0:56 ` Laura Abbott [this message]
2014-08-28 1:17 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-08-27 4:29 Stephen Rothwell
2024-08-27 6:09 Stephen Rothwell
2021-08-27 11:24 Stephen Rothwell
2020-08-27 5:11 Stephen Rothwell
2020-08-27 8:37 ` Anders Roxell
2020-08-27 17:02 ` Atish Patra
2020-08-27 17:03 ` Palmer Dabbelt
2019-08-27 9:05 Stephen Rothwell
2018-08-27 1:01 Stephen Rothwell
2018-08-27 1:00 Stephen Rothwell
2015-08-27 8:22 Stephen Rothwell
2013-08-27 10:30 Stephen Rothwell
2013-08-27 10:30 ` Stephen Rothwell
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=53FE7E2D.9060408@codeaurora.org \
--to=lauraa@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.