From: Guenter Roeck <linux@roeck-us.net>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: Tree for Oct 22
Date: Tue, 22 Oct 2013 12:24:03 -0700 [thread overview]
Message-ID: <20131022192403.GB28630@roeck-us.net> (raw)
In-Reply-To: <1382454517-4074-1-git-send-email-treding@nvidia.com>
On Tue, Oct 22, 2013 at 05:08:34PM +0200, Thierry Reding wrote:
> Hi all,
>
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>
> git://gitorious.org/thierryreding/linux-next.git
>
> A next-20131022 tag is also provided for convenience.
>
> Gained a couple new conflicts, fixed more build failures. ARM seems to
> be in pretty good shape, as is the 64-bit x86 allmodconfig.
>
x86_64:defconfig, i386:allyesconfig and i386:allmodconfig fail to build.
lib/built-in.o: In function `trace_swiotlb_bounced':
include/trace/events/swiotlb.h:9: undefined reference to `__tracepoint_swiotlb_bounced'
and
lib/built-in.o: In function `swiotlb_map_page':
(.text+0x10c94): undefined reference to `__tracepoint_swiotlb_bounced'
arm:allmodconfig fails as well, currently with
arch/arm/common/bL_switcher.c: In function 'bL_switcher_enable':
arch/arm/common/bL_switcher.c:580:2: error: implicit declaration of function
'cpu_hotplug_driver_lock' [-Werror=implicit-function-declaration]
arch/arm/common/bL_switcher.c:582:3: error: implicit declaration of function
'cpu_hotplug_driver_unlock' [-Werror=implicit-function-declaration]
Overall, failures are up to
total: 110 pass: 88 skipped: 4 fail: 18
from 14 failures yesterday.
Guenter
next prev parent reply other threads:[~2013-10-22 19:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 15:08 linux-next: Tree for Oct 22 Thierry Reding
2013-10-22 15:08 ` linux-next: manual merge of the arm tree Thierry Reding
2013-10-22 15:08 ` Thierry Reding
2013-10-25 15:20 ` Dmitry Kravkov
2013-10-22 15:08 ` linux-next: manual merge of the ipsec-next tere Thierry Reding
2013-10-22 15:08 ` linux-next: manual merge of the usb tree Thierry Reding
2013-10-22 18:02 ` Srinivas Pandruvada
2013-10-22 19:24 ` Guenter Roeck [this message]
2013-10-22 22:04 ` linux-next: Tree for Oct 22 (xilinx_uartps) Randy Dunlap
2013-10-23 7:04 ` Greg Kroah-Hartman
2013-10-22 22:36 ` linux-next: Tree for Oct 22 (crypto/asymmetric_keys/rsa.c) Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2025-10-22 3:18 linux-next: Tree for Oct 22 Stephen Rothwell
2024-10-22 7:36 Stephen Rothwell
2021-10-22 9:15 Stephen Rothwell
2020-10-22 3:41 Stephen Rothwell
2019-10-22 5:24 Stephen Rothwell
2015-10-22 5:45 Stephen Rothwell
2014-10-22 3:42 Stephen Rothwell
2012-10-22 4:36 Stephen Rothwell
2012-10-22 4:36 ` 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=20131022192403.GB28630@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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.