From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: linux-xtensa@linux-xtensa.org,
the arch/x86 maintainers <x86@kernel.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Build regressions/improvements in v3.6-rc3
Date: Thu, 23 Aug 2012 22:50:22 +0200 [thread overview]
Message-ID: <CAMuHMdWFY_iOXTfLO7zCm_RTdkEjj7BpT5o9pJ6cu3LdT8JsYQ@mail.gmail.com> (raw)
In-Reply-To: <1345754768-4634-1-git-send-email-geert@linux-m68k.org>
On Thu, Aug 23, 2012 at 10:46 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> JFYI, when comparing v3.6-rc3 to v3.6-rc2[3], the summaries are:
> - build errors: +13/-9
+ arch/x86/include/asm/uaccess_32.h: error: call to
'copy_from_user_overflow' declared with attribute error:
copy_from_user() buffer size is not provably correct: => 211:26
i386_defconfig, i386-randconfig, x86_64_defconfig
+ drivers/extcon/extcon_gpio.c: error: implicit declaration of
function 'devm_gpio_request_one'
[-Werror=implicit-function-declaration]: => 110:2
xtensa-allmodconfig
+ error: No rule to make target drivers/scsi/aic7xxx/aicasm/*.[chyl]: => N/A
i386-randconfig
+ error: eni.c: relocation truncated to fit: R_PPC64_REL24 against
symbol `._raw_read_lock' defined in .spinlock.text section in
kernel/built-in.o: => (.text+0x1ff91bc)
+ error: eni.c: relocation truncated to fit: R_PPC64_REL24 against
symbol `.sprintf' defined in .text section in lib/lib.a(vsprintf.o):
=> (.text+0x1ff940c)
+ error: eni.c: relocation truncated to fit: R_PPC64_REL24 against
symbol `_restgpr0_16' defined in .text.save.restore section in
arch/powerpc/lib/built-in.o: => (.text+0x1ffa6e8)
+ error: eni.c: relocation truncated to fit: R_PPC64_REL24 against
symbol `_savegpr0_27' defined in .text.save.restore section in
arch/powerpc/lib/built-in.o: => (.text+0x1ff9854)
+ error: eni.c: relocation truncated to fit: R_PPC64_REL24 against
symbol `_savegpr0_30' defined in .text.save.restore section in
arch/powerpc/lib/built-in.o: => (.text+0x1ff8eb4), (.text+0x1ff8e80)
+ error: fore200e.c: relocation truncated to fit: R_PPC64_REL24
against symbol `._raw_spin_unlock_irqrestore' defined in
.spinlock.text section in kernel/built-in.o: => (.text+0x1ff82cc),
(.text+0x1ff8278)
+ error: fore200e.c: relocation truncated to fit: R_PPC64_REL24
against symbol `.mutex_unlock' defined in .sched.text section in
kernel/built-in.o: => (.text+0x1ff83fc), (.text+0x1ff83a8)
powerpc-allyesconfig
+ error: via-pmu-event.c: undefined reference to
`.input_allocate_device': => .init.text+0xdfbc)
+ error: via-pmu-event.c: undefined reference to
`.input_free_device': => .init.text+0xe084)
+ error: via-pmu-event.c: undefined reference to
`.input_register_device': => .init.text+0xe06c)
powerpc-randconfig
> [1] http://kisskb.ellerman.id.au/kisskb/head/5359/ (all 116 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/head/5338/ (all 116 configs)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
parent reply other threads:[~2012-08-23 20:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1345754768-4634-1-git-send-email-geert@linux-m68k.org>]
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=CAMuHMdWFY_iOXTfLO7zCm_RTdkEjj7BpT5o9pJ6cu3LdT8JsYQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).