All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: David Miller <davem@davemloft.net>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 4.19-rc2
Date: Mon, 3 Sep 2018 12:36:14 -0700	[thread overview]
Message-ID: <236bb7e7-2f9e-880d-a30e-9acf9bdc9bcf@roeck-us.net> (raw)
In-Reply-To: <20180903.120910.2227273252885975717.davem@davemloft.net>

On 09/03/2018 12:09 PM, David Miller wrote:
> From: Guenter Roeck <linux@roeck-us.net>
> Date: Mon, 3 Sep 2018 11:22:02 -0700
> 
>> The sparc32:allmodconfig build problem is the same as last week.
>> David - any interest/plan to get this fixed, or should I just drop
>> the build ?
> 
> I didn't see it, please give me a reference to the details.
> 

arch/sparc/kernel/head_32.o: In function `current_pc':
arch/sparc/kernel/.tmp_head_32.o:(.head.text+0x5040): relocation truncated to fit: R_SPARC_WDISP22 against `.init.text'
arch/sparc/kernel/head_32.o: In function `halt_notsup':
arch/sparc/kernel/.tmp_head_32.o:(.head.text+0x5100): relocation truncated to fit: R_SPARC_WDISP22 against `.init.text'
arch/sparc/kernel/head_32.o: In function `leon_init':
arch/sparc/kernel/.tmp_head_32.o:(.init.text+0xa4): relocation truncated to fit: R_SPARC_WDISP22 against symbol `leon_smp_cpu_startup' defined in .text section in arch/sparc/kernel/trampoline_32.o
arch/sparc/kernel/process_32.o:(.fixup+0x4): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/process_32.o:(.fixup+0xc): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x0): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x8): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x10): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x18): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x20): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x28): additional relocation overflows omitted from the output
make[1]: *** [vmlinux] Error 1
make: *** [sub-make] Error 2

The most recent log is at
	https://kerneltests.org/builders/hwmon-sparc32-master/builds/1024/steps/buildcommand/logs/stdio

Build history is at
	https://kerneltests.org/builders/hwmon-sparc32-master

Guenter

  reply	other threads:[~2018-09-03 19:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 21:45 Linux 4.19-rc2 Linus Torvalds
2018-09-03 18:22 ` Guenter Roeck
2018-09-03 19:09   ` David Miller
2018-09-03 19:36     ` Guenter Roeck [this message]
2018-09-11  7:53 ` [REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2) Martin Steigerwald
2018-09-11  8:17   ` Rafael J. Wysocki
2018-09-11 10:17     ` Martin Steigerwald
2018-09-12 17:10       ` [Intel-gfx] " Ville Syrjälä
2018-09-12 17:10         ` Ville Syrjälä
2018-09-12 21:03         ` [Intel-gfx] " Martin Steigerwald
2018-10-26 15:43   ` Martin Steigerwald
2018-10-30  6:41     ` Rafael J. Wysocki

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=236bb7e7-2f9e-880d-a30e-9acf9bdc9bcf@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.