linux-next.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 Oct 1
Date: Wed, 1 Oct 2014 20:59:24 -0700	[thread overview]
Message-ID: <20141002035924.GA18144@roeck-us.net> (raw)
In-Reply-To: <20141001175411.00be9683@canb.auug.org.au>

On Wed, Oct 01, 2014 at 05:54:11PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20140930:
> 
> The arm-soc tree still had its build failure for which I reverted
> 5 commits.
> 
> The net-next tree gained a conflict against the berlin tree, lost
> its build failure but gained another for which I applied a patch.
> 
> The vfio tree gained a conflict against the pci tree.
> 
> The tty tree lost its build failure.
> 
> The staging tree still had its build failure for which I reverted
> a commit.
> 
> The gpio tree gained conflicts against Linus' tree and the pinctrl tree.
> 
> The akpm tree lost a patch that turned up elsewhere.
> 
> Non-merge commits (relative to Linus' tree): 8953
>  7726 files changed, 354879 insertions(+), 267353 deletions(-)
> 
> ----------------------------------------------------------------------------
> 
Building arm:cm_x2xx_defconfig ... failed

drivers/built-in.o: In function `clk_set_rate':
:(.text+0xdef44): multiple definition of `clk_set_rate'
arch/arm/mach-pxa/built-in.o::(.text+0xf78): first defined here
drivers/built-in.o:(___ksymtab_gpl+clk_disable+0x0): multiple definition of
`__ksymtab_clk_disable'
arch/arm/mach-pxa/built-in.o:(___ksymtab+clk_disable+0x0): first defined here
drivers/built-in.o: In function `clk_disable':
:(.text+0xddf30): multiple definition of `clk_disable'
arch/arm/mach-pxa/built-in.o::(.text+0xfbc): first defined here

[and more]

---
Building m68k:allmodconfig ... failed

drivers/media/rc/ir-hix5hd2.c: In function 'hix5hd2_ir_config':
drivers/media/rc/ir-hix5hd2.c:100:2: error: implicit declaration of function 'readl_relaxed'

---
Building mn10300:asb2303_defconfig ... failed
Building um:defconfig ... failed

In file included from drivers/base/platform.c:24:0:
include/linux/pm_domain.h:74:23: error: expected identifier or '(' before '&' token
make[2]: *** [drivers/base/platform.o] Error 1

---
Building sparc64:allmodconfig ... failed

drivers/bcma/main.c: In function 'bcma_of_find_child_device':
drivers/bcma/main.c:150:3: error: implicit declaration of function 'of_translate_address'

---

Guenter

  reply	other threads:[~2014-10-02  3:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01  7:54 linux-next: Tree for Oct 1 Stephen Rothwell
2014-10-02  3:59 ` Guenter Roeck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-01  7:09 Stephen Rothwell
2020-10-01 11:39 Stephen Rothwell
2019-10-01  2:13 Stephen Rothwell
2015-10-01  6:50 Stephen Rothwell
2013-10-01 11:03 Thierry Reding
2012-10-01 15:03 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=20141002035924.GA18144@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).