From: Timur Tabi <timur@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
<linux-kernel@vger.kernel.org>,
Linuxppc-dev <linuxppc-dev@ozlabs.org>,
the arch/x86 maintainers <x86@kernel.org>,
Parisc List <linux-parisc@vger.kernel.org>,
Scott Wood <scottwood@freescale.com>,
Kumar Gala <galak@kernel.crashing.org>
Subject: Re: Re: Build regressions/improvements in v3.4-rc7
Date: Thu, 17 May 2012 13:42:44 -0500 [thread overview]
Message-ID: <4FB546A4.7090502@freescale.com> (raw)
In-Reply-To: <1337212281.30558.17.camel@pasglop>
Benjamin Herrenschmidt wrote:
> + arch/powerpc/platforms/512x/mpc512x_shared.c: error: 'enum
>> fsl_diu_monitor_port' declared inside parameter list [-Werror]: =>
>> 70:9, 84:9, 88:36
>> + arch/powerpc/platforms/512x/mpc512x_shared.c: error: 'return' with
>> a value, in function returning void [-Werror]: => 189:2
>> + arch/powerpc/platforms/512x/mpc512x_shared.c: error: function
>> declaration isn't a prototype [-Werror=strict-prototypes]: => 69:5,
>> 88:6, 83:6, 187:1
>> + arch/powerpc/platforms/512x/mpc512x_shared.c: error: its scope is
>> only this definition or declaration, which is probably not what you
>> want [-Werror]: => 70:9
So I think I have a fix for these, but I still would like the actual
.config so that I can be sure.
>> + drivers/virt/fsl_hypervisor.c: error: 'MSR_GS' undeclared (first
>> use in this function): => 799:80
I can't reproduce this one. MSR_GS is defined in reg_booke.h.
fsl_hypervisor.c should not be compiled on a non-booke platform. I don't
know if the fix is to add this to fsl_hypervisor.c:
#include <asm/reg_booke.h>
or if I should update the Kconfig:
config FSL_HV_MANAGER
tristate "Freescale hypervisor management driver"
depends on FSL_SOC
to
depends on FSL_BOOKE
or maybe
depends on FSL_BOOKE && FSL_SOC
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Parisc List <linux-parisc@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
linux-kernel@vger.kernel.org,
Linuxppc-dev <linuxppc-dev@ozlabs.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Scott Wood <scottwood@freescale.com>
Subject: Re: Re: Build regressions/improvements in v3.4-rc7
Date: Thu, 17 May 2012 13:42:44 -0500 [thread overview]
Message-ID: <4FB546A4.7090502@freescale.com> (raw)
In-Reply-To: <1337212281.30558.17.camel@pasglop>
Benjamin Herrenschmidt wrote:
> + arch/powerpc/platforms/512x/mpc512x_shared.c: error: 'enum
>> fsl_diu_monitor_port' declared inside parameter list [-Werror]: =>
>> 70:9, 84:9, 88:36
>> + arch/powerpc/platforms/512x/mpc512x_shared.c: error: 'return' with
>> a value, in function returning void [-Werror]: => 189:2
>> + arch/powerpc/platforms/512x/mpc512x_shared.c: error: function
>> declaration isn't a prototype [-Werror=strict-prototypes]: => 69:5,
>> 88:6, 83:6, 187:1
>> + arch/powerpc/platforms/512x/mpc512x_shared.c: error: its scope is
>> only this definition or declaration, which is probably not what you
>> want [-Werror]: => 70:9
So I think I have a fix for these, but I still would like the actual
.config so that I can be sure.
>> + drivers/virt/fsl_hypervisor.c: error: 'MSR_GS' undeclared (first
>> use in this function): => 799:80
I can't reproduce this one. MSR_GS is defined in reg_booke.h.
fsl_hypervisor.c should not be compiled on a non-booke platform. I don't
know if the fix is to add this to fsl_hypervisor.c:
#include <asm/reg_booke.h>
or if I should update the Kconfig:
config FSL_HV_MANAGER
tristate "Freescale hypervisor management driver"
depends on FSL_SOC
to
depends on FSL_BOOKE
or maybe
depends on FSL_BOOKE && FSL_SOC
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-05-17 18:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 8:30 Build regressions/improvements in v3.4-rc7 Geert Uytterhoeven
2012-05-16 8:47 ` Geert Uytterhoeven
2012-05-16 8:47 ` Geert Uytterhoeven
2012-05-16 8:47 ` Geert Uytterhoeven
2012-05-16 14:46 ` James Bottomley
2012-05-16 14:46 ` James Bottomley
2012-05-16 15:59 ` Kasatkin, Dmitry
2012-05-16 15:59 ` Kasatkin, Dmitry
2012-05-16 15:59 ` Kasatkin, Dmitry
2012-05-16 15:59 ` Geert Uytterhoeven
2012-05-16 15:59 ` Geert Uytterhoeven
2012-05-16 15:59 ` Geert Uytterhoeven
2012-05-17 0:27 ` John David Anglin
2012-05-17 0:27 ` John David Anglin
2012-05-16 23:51 ` Benjamin Herrenschmidt
2012-05-16 23:51 ` Benjamin Herrenschmidt
2012-05-17 17:30 ` Timur Tabi
2012-05-17 17:30 ` Timur Tabi
2012-05-17 17:52 ` Tabi Timur-B04825
2012-05-17 17:52 ` Tabi Timur-B04825
2012-05-17 17:52 ` Tabi Timur-B04825
2012-05-17 18:42 ` Geert Uytterhoeven
2012-05-17 18:42 ` Geert Uytterhoeven
2012-05-17 18:42 ` Geert Uytterhoeven
2012-05-17 18:44 ` Timur Tabi
2012-05-17 18:44 ` Timur Tabi
2012-05-17 18:48 ` Scott Wood
2012-05-17 18:48 ` Scott Wood
2012-05-17 18:51 ` Timur Tabi
2012-05-17 18:51 ` Timur Tabi
2012-05-17 18:42 ` Timur Tabi [this message]
2012-05-17 18:42 ` Timur Tabi
2012-05-18 7:47 ` Michael Ellerman
2012-05-18 7:47 ` Michael Ellerman
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=4FB546A4.7090502@freescale.com \
--to=timur@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--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 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.