From: Oleksij Rempel <linux@rempel-privat.de>
To: Guenter Roeck <linux@roeck-us.net>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthew Wilcox <matthew.r.wilcox@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: Re: linux-next: Tree for Jan 30 (build failures)
Date: Fri, 30 Jan 2015 17:01:58 +0100 [thread overview]
Message-ID: <54CBAAF6.6030106@rempel-privat.de> (raw)
In-Reply-To: <20150130142520.GA6872@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
Hi Guenter,
Am 30.01.2015 um 15:25 schrieb Guenter Roeck:
> On Fri, Jan 30, 2015 at 06:02:09PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20150129:
>>
>> The arm-soc gained conflicts against the arm-current and arm trees.
>>
>> The spi tree gained a build failure for which I reverted a commit.
>>
>> Non-merge commits (relative to Linus' tree): 6300
>> 6348 files changed, 255117 insertions(+), 131620 deletions(-)
>>
>> ----------------------------------------------------------------------------
>
> Build failures below. I copied the culprits (including Linus ;-).
>
> Guenter
>
> ===
> Building arc:defconfig ... failed
> Building arc:tb10x_defconfig ... failed
> --------------
> Error log:
> arch/arc/mm/fault.c: In function 'do_page_fault':
> arch/arc/mm/fault.c:164: error: 'VM_FAULT_SIGSEV' undeclared
>
> Typo. Caused by 33692f27597f ("vm: add VM_FAULT_SIGSEGV handling support"),
> from mainline. I submitted a patch.
>
> ===
> Building mips:allmodconfig ... failed
> --------------
> Error log:
>
> fs/built-in.o: In function `dax_fault':
> (.text+0x5e284): undefined reference to `copy_user_page'
>
> Caused by 4927b7d77c001 ("dax,ext2: replace the XIP page fault handler with the
> DAX page fault handler"). Looks like copy_user_page does not exist in mips.
>
> ===
> Building sparc64:allmodconfig ... failed
> --------------
> Error log:
> drivers/built-in.o: In function `asm9260_timer_init':
> asm9260_timer.c:(.init.text+0x60d4): undefined reference to `of_io_request_and_map'
>
> Caused by e4940cd76934 ("ARM: clocksource: add asm9260_timer driver").
> of_io_request_and_map does not exist for the sparc architecture.
> Maybe that driver should depend on ARM or at least on !SPARC ?
White listing will be easiest way. Should i send patch for it, or it is
better to fixup existing patch?
--
Regards,
Oleksij
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next prev parent reply other threads:[~2015-01-30 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 7:02 linux-next: Tree for Jan 30 Stephen Rothwell
2015-01-30 14:25 ` linux-next: Tree for Jan 30 (build failures) Guenter Roeck
2015-01-30 16:01 ` Oleksij Rempel [this message]
2015-01-30 17:30 ` Guenter Roeck
2015-01-31 8:13 ` [PATCH] ARM: clocksource: whitelist asm9260_timer driver for ARM Oleksij Rempel
2015-01-30 16:15 ` linux-next: Tree for Jan 30 (build failures) Boris Brezillon
2015-01-30 19:07 ` linux-next: Tree for Jan 30 (clk related WARNING on arm) Guenter Roeck
2015-02-01 9:23 ` Geert Uytterhoeven
2015-02-01 18:49 ` Guenter Roeck
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=54CBAAF6.6030106@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthew.r.wilcox@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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