From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
stable <stable@vger.kernel.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: [ 00/17] 3.4.58-stable review
Date: Fri, 16 Aug 2013 15:39:50 -0700 [thread overview]
Message-ID: <20130816223950.GA9152@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdW6Ji7ibMeQj5FBQsJS3B-WWx=Lbhmjx4CCFEGg_uobHQ@mail.gmail.com>
On Fri, Aug 16, 2013 at 11:55:02PM +0200, Geert Uytterhoeven wrote:
> On Fri, Aug 16, 2013 at 10:27 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> > Still failing:
> > sparc64:allmodconfig
> > /opt/buildbot/slave/stable-queue-3_4/build/usr/include/linux/types.h:27:1: error: unknown type name ‘__u16’
>
> According to my log collection, this same error message was fixed in v3.3-rc2,
> but I couldn't easily find a matching commit.
> But this is v3.4-stable, which is after v3.3-rc2, so it got reintroduced?
>
It was fixed recently with
commit cbf1ef6b3345d2cc7e62407eec6a6f72a8b1346f
Author: Sam Ravnborg <sam@ravnborg.org>
Date: Sun Mar 31 07:01:47 2013 +0000
sparc: use asm-generic version of types.h
and
commit a2d34dd41212032c03e77bc30c2023725def841a
Author: Sam Ravnborg <sam@ravnborg.org>
Date: Sat Mar 30 11:44:22 2013 +0000
sparc: use generic headers
I tried to apply those patches, but it failed miserably due to the
userspace/kernel header separation. Given that, I figured that
it would be too invasive to fix, at least for me.
> > xtensa:defconfig
> > dev.c:(.text.unlikely+0x3): dangerous relocation: l32r: literal placed after use: .literal.unlikely
>
> Fixed in v3.7-rc1:
>
> commit f6a03a12ecdbe0dd80a55f6df3b7206c5a403a49
> Author: Max Filippov <jcmvbkbc@gmail.com>
> Date: Mon Sep 17 05:44:31 2012 +0400
>
> xtensa: fix linker script transformation for .text.unlikely
>
Yes, that fixes this problem, except now we get another known error:
kernel/built-in.o:(.text+0x8c8): undefined reference to `_sdata'
which you had fixed with
commit 5e7b6ed8e9bf3c8e3bb579fd0aec64f6526f8c81
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date: Wed Jun 20 12:52:58 2012 -0700
xtensa: replace xtensa-specific _f{data,text} by _s{data,text}
After applying both patches to the 3.4-stable queue, xtensa:defconfig builds
successfully.
Thanks,
Guenter
next prev parent reply other threads:[~2013-08-16 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130813063501.728847844@linuxfoundation.org>
[not found] ` <520A1D56.2050507@roeck-us.net>
[not found] ` <20130813175858.GC7336@kroah.com>
[not found] ` <20130813201936.GA18358@roeck-us.net>
[not found] ` <20130815063158.GB25754@kroah.com>
[not found] ` <520C86BD.2020903@roeck-us.net>
2013-08-15 7:55 ` [ 00/17] 3.4.58-stable review Geert Uytterhoeven
2013-08-15 8:05 ` Guenter Roeck
2013-08-16 4:53 ` Guenter Roeck
2013-08-16 5:10 ` Greg Kroah-Hartman
2013-08-16 8:26 ` Guenter Roeck
2013-08-16 12:41 ` Greg Kroah-Hartman
2013-08-16 20:27 ` Guenter Roeck
2013-08-16 21:55 ` Geert Uytterhoeven
2013-08-16 22:39 ` Guenter Roeck [this message]
2013-08-16 23:08 ` Greg Kroah-Hartman
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=20130816223950.GA9152@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox