linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 27
Date: Wed, 27 Aug 2014 16:58:09 -0700	[thread overview]
Message-ID: <20140827235809.GA9598@roeck-us.net> (raw)
In-Reply-To: <20140827161021.298aede6@canb.auug.org.au>

On Wed, Aug 27, 2014 at 04:10:21PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20140826:
> 
> The net tree lost its build failure.
> 
> The usb.current tree gained a build failure for which I reverted a commit.
> 
> The mfd tree lost its build failure.
> 
> The percpu tree gained a build failure so I used the version from
> next-20140826.
> 
> The staging tree still had its build failure for which I applied a
> fix patch.
> 
> The akpm-current tree lost its build failure.
> 
> The akpm tree lost its build failure and a patch that turned up elsewhere.
> 
> Non-merge commits (relative to Linus' tree): 2028
>  2105 files changed, 56310 insertions(+), 35111 deletions(-)
> 
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

Guenter


  reply	other threads:[~2014-08-27 23:58 UTC|newest]

Thread overview: 15+ 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 [this message]
2014-08-28  0:48   ` Stephen Rothwell
2014-08-28  0:56     ` Laura Abbott
2014-08-28  1:17       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
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

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=20140827235809.GA9598@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 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).