From: Scott Wood <scottwood@freescale•com>
To: Geert Uytterhoeven <geert@linux-m68k•org>
Cc: linuxppc-dev@lists•ozlabs.org, linux-kernel@vger•kernel.org
Subject: Re: Build regressions/improvements in v3.7-rc5
Date: Mon, 12 Nov 2012 15:51:06 -0600 [thread overview]
Message-ID: <1352757066.32153.5@snotra> (raw)
In-Reply-To: <CAMuHMdXE0yJNivpirGgx08zqLH2086ydeOU6zswXj-+zn8OsWQ@mail.gmail.com> (from geert@linux-m68k.org on Mon Nov 12 15:02:46 2012)
On 11/12/2012 03:02:46 PM, Geert Uytterhoeven wrote:
> On Mon, Nov 12, 2012 at 9:58 PM, Geert Uytterhoeven
> <geert@linux-m68k•org> wrote:
> > JFYI, when comparing v3.7-rc5 to v3.7-rc4[3], the summaries are:
> > - build errors: +14/-4
>=20
> 14 regressions:
> + drivers/virt/fsl_hypervisor.c: error: 'MSR_GS' undeclared (first
> use in this function): =3D> 799:93
These reports would be more useful if the actual .config were provided, =20
rather than just saying "powerpc randconfig".
I doubt this particular one is a regression; it looks like the =20
dependencies have always been too weak (patch sent) and you're just =20
comparing different randomly-generated configs.
> powerpc-randconfig
>=20
> + error: relocation truncated to fit: R_PPC64_REL24 against symbol
> `._mcount' defined in .text section in arch/powerpc/kernel/entry_64.o:
> (.text+0x1ff9eb8) =3D> (.text+0x1ffa274), (.text+0x1ff7840)
>=20
> powerpc-allyesconfig
It's been over 3 years since powerpc-allyesconfig built (it's just too =20
big for the relocation model the kernel uses) -- how is this a =20
regression?
-Scott=
next prev parent reply other threads:[~2012-11-12 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1352753886-3402-1-git-send-email-geert@linux-m68k.org>
2012-11-12 21:02 ` Build regressions/improvements in v3.7-rc5 Geert Uytterhoeven
2012-11-12 21:51 ` Scott Wood [this message]
2012-11-13 10:39 ` Geert Uytterhoeven
2012-11-12 22:05 ` 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=1352757066.32153.5@snotra \
--to=scottwood@freescale$(echo .)com \
--cc=geert@linux-m68k$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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