Hi Madhavan,
On Tue, 22 Apr 2025 11:20:38 +0530 Madhavan Srinivasan
wrote:
>
> I cant recreate this in both my x86_64 cross build and ppc64 build with dash.
> I tried both ppc64_defconfig and pseries_le_defconfig compilation.
>
> x86_64 dash version : dash-0.5.12-3.fc40.x86_64
> powerpc dash ve
On 4/22/25 7:17 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the powerpc-fixes tree, today's linux-next build
> (powerpc_ppc64_defconfig) produced these warnings:
>
> arch/powerpc/boot/wrapper: 237: [: 0: unexpected operator
> ld: warning: arch/powerpc/boot/zImage.epapr has a LOAD s
Stephen Rothwell writes:
> Hi all,
>
> Today's (and a few before) linux-next build (powerpc pseries_le_defconfig)
> produced these warnings:
Those aren't really warnings, it's just merge_config.sh telling you what
it's doing. The whole point of the generated configs is to override
those symbols.
Sathvika Vasireddy wrote:
On 29/11/22 20:58, Christophe Leroy wrote:
Le 29/11/2022 à 16:13, Sathvika Vasireddy a écrit :
Hi all,
On 25/11/22 09:00, Stephen Rothwell wrote:
Hi all,
After merging the powerpc-objtool tree, today's linux-next build (powerpc
pseries_le_defconfig) produced these
On 29/11/22 20:58, Christophe Leroy wrote:
Le 29/11/2022 à 16:13, Sathvika Vasireddy a écrit :
Hi all,
On 25/11/22 09:00, Stephen Rothwell wrote:
Hi all,
After merging the powerpc-objtool tree, today's linux-next build (powerpc
pseries_le_defconfig) produced these warnings:
arch/powerpc/k
Le 29/11/2022 à 16:13, Sathvika Vasireddy a écrit :
> Hi all,
>
> On 25/11/22 09:00, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the powerpc-objtool tree, today's linux-next build (powerpc
>> pseries_le_defconfig) produced these warnings:
>>
>> arch/powerpc/kernel/head_64.o: warning:
Hi all,
On 25/11/22 09:00, Stephen Rothwell wrote:
Hi all,
After merging the powerpc-objtool tree, today's linux-next build (powerpc
pseries_le_defconfig) produced these warnings:
arch/powerpc/kernel/head_64.o: warning: objtool: end_first_256B(): can't find
starting instruction
arch/powerpc/k
On Thu, 14 Oct 2021 10:44:46 +0200
Arnd Bergmann a...@arndb.de wrote:
>On Thu, Oct 14, 2021 at 12:12 AM Anatolij Gustschin wrote:
>> On Tue, 12 Oct 2021 16:39:56 +0200
>> Arnd Bergmann a...@arndb.de wrote:
>> ...
>> >Grant Likely was the original maintainer for MPC52xx until 2011,
>> >Anatolij
On Thu, Oct 14, 2021 at 12:12 AM Anatolij Gustschin wrote:
> On Tue, 12 Oct 2021 16:39:56 +0200
> Arnd Bergmann a...@arndb.de wrote:
> ...
> >Grant Likely was the original maintainer for MPC52xx until 2011,
> >Anatolij Gustschin is still listed as maintainer since then but hasn't
> >been active in
On Wed, Oct 13, 2021 at 5:28 PM Anatolij Gustschin wrote:
>
> On Wed, 13 Oct 2021 17:17:25 -0500
> Rob Herring robh...@kernel.org wrote:
> ...
> >In general, you shouldn't need to be changing the drivers. Can you
> >tell me which warnings need driver changes?
>
> ethernet and mdio drivers share re
On Wed, 13 Oct 2021 17:17:25 -0500
Rob Herring robh...@kernel.org wrote:
...
>In general, you shouldn't need to be changing the drivers. Can you
>tell me which warnings need driver changes?
ethernet and mdio drivers share registers, so they use same unit-address:
arch/powerpc/boot/dts/tqm5200.dts
On Wed, Oct 13, 2021 at 5:12 PM Anatolij Gustschin wrote:
>
> Hi Arnd, Rob,
>
> On Tue, 12 Oct 2021 16:39:56 +0200
> Arnd Bergmann a...@arndb.de wrote:
> ...
> >Grant Likely was the original maintainer for MPC52xx until 2011,
> >Anatolij Gustschin is still listed as maintainer since then but hasn'
Hi Arnd, Rob,
On Tue, 12 Oct 2021 16:39:56 +0200
Arnd Bergmann a...@arndb.de wrote:
...
>Grant Likely was the original maintainer for MPC52xx until 2011,
>Anatolij Gustschin is still listed as maintainer since then but hasn't
>been active in it for a while either. Anatolij can probably best judge
On Mon, Oct 11, 2021 at 10:42 PM Rob Herring wrote:
> On Sun, Oct 10, 2021 at 4:27 PM Stephen Rothwell
> wrote:
> FYI, u-boot removed mpc5xxx support in 2017, so maybe there's
> similarly not a need to keep them in the kernel? It does appear NXP
> will still sell you the parts though the last BS
+Arnd in regards to removing platforms.
On Sun, Oct 10, 2021 at 4:27 PM Stephen Rothwell wrote:
>
> Hi all,
>
> [Cc'ing Rob]
>
> Rob: these warnings have been there for a long time ...
If anyone cares about these platforms, then the warnings should be
fixed by folks that care. If not, then perha
Hi all,
[Cc'ing Rob]
Rob: these warnings have been there for a long time ...
On Fri, 8 Oct 2021 16:47:28 +1100 Stephen Rothwell
wrote:
>
> Hi all,
>
> After merging the origin tree, today's linux-next build (powerpc
> allyesconfig) produced these warnings (along with many others):
>
> arch/p
Hi Masahiro,
On Wed, 4 Sep 2019 15:22:09 +0900 Masahiro Yamada
wrote:
>
> For today's linux-next, please squash the following too.
>
> (This is my fault, since scripts/mkuboot.sh is a bash script)
>
>
> diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
> index 41c50f9461e5..2d72327417a
Hi Masahiro,
On Wed, 4 Sep 2019 10:00:30 +0900 Masahiro Yamada
wrote:
>
> Could you fix it up as follows?
> I will squash it for tomorrow's linux-next.
>
>
> --- a/arch/powerpc/Makefile.postlink
> +++ b/arch/powerpc/Makefile.postlink
> @@ -18,7 +18,7 @@ quiet_cmd_relocs_check = CHKREL $@
> i
On Wed, Sep 4, 2019 at 10:00 AM Masahiro Yamada
wrote:
>
> Hi Stephen,
>
> On Wed, Sep 4, 2019 at 9:13 AM Stephen Rothwell wrote:
> >
For today's linux-next, please squash the following too.
(This is my fault, since scripts/mkuboot.sh is a bash script)
diff --git a/scripts/Makefile.lib b/scri
Hi Stephen,
On Wed, Sep 4, 2019 at 9:13 AM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the kbuild tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
>
> Presumably introduced by commit
>
> 1267f9d3047d ("kbuild: add $(BASH) to run scripts with bash-e
On Sun, 18 Nov 2018 at 21:52, Alan Modra wrote:
>
> On Wed, Nov 14, 2018 at 09:20:23PM +1100, Michael Ellerman wrote:
> > Joel Stanley writes:
> > > Hello Alan,
> > >
> > > On Tue, 12 Jun 2018 at 07:44, Stephen Rothwell
> > > wrote:
> > >
> > >> Building Linus' tree, today's linux-next build (p
On Wed, Nov 14, 2018 at 09:20:23PM +1100, Michael Ellerman wrote:
> Joel Stanley writes:
> > Hello Alan,
> >
> > On Tue, 12 Jun 2018 at 07:44, Stephen Rothwell
> > wrote:
> >
> >> Building Linus' tree, today's linux-next build (powerpc ppc64_defconfig)
> >> produced these warning:
> >>
> >> ld:
Joel Stanley writes:
> Hello Alan,
>
> On Tue, 12 Jun 2018 at 07:44, Stephen Rothwell wrote:
>
>> Building Linus' tree, today's linux-next build (powerpc ppc64_defconfig)
>> produced these warning:
>>
>> ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in
>> section `.gnu
Hello Alan,
On Tue, 12 Jun 2018 at 07:44, Stephen Rothwell wrote:
> Building Linus' tree, today's linux-next build (powerpc ppc64_defconfig)
> produced these warning:
>
> ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in
> section `.gnu.hash'.
> ld: warning: orphan sec
Stephen Rothwell writes:
> On Tue, 02 May 2017 19:53:25 +1000 Michael Ellerman
> wrote:
>>
>> Though we are supposed to be building with -Werror, so those should be
>> breaking the build. I assume you have turned Werror off?
>
> I assume that allyesconfig turns on CONFIG_PPC_DISABLE_WERROR ...
Hi Michael,
On Tue, 2 May 2017 21:17:01 +1000 Stephen Rothwell
wrote:
>
> On Tue, 02 May 2017 19:53:25 +1000 Michael Ellerman
> wrote:
> >
> > Though we are supposed to be building with -Werror, so those should be
> > breaking the build. I assume you have turned Werror off?
>
> I assume tha
Hi Michael,
On Tue, 02 May 2017 19:53:25 +1000 Michael Ellerman wrote:
>
> Though we are supposed to be building with -Werror, so those should be
> breaking the build. I assume you have turned Werror off?
I assume that allyesconfig turns on CONFIG_PPC_DISABLE_WERROR ...
--
Cheers,
Stephen Rothw
Stephen Rothwell writes:
> Hi all,
>
> The linux-next build (powerpc allyesconfig) produced these warnings
> (and have for a while):
>
> arch/powerpc/kvm/book3s_pr_papr.c: In function 'kvmppc_h_pr_enter':
> arch/powerpc/kvm/book3s_pr_papr.c:53:2: warning: ignoring return value of
> 'copy_from_us
On Fri, Aug 26, 2016 at 01:58:03PM +1000, Nicholas Piggin wrote:
> On Mon, 22 Aug 2016 20:47:58 +1000
> Nicholas Piggin wrote:
>
> > On Fri, 19 Aug 2016 20:44:55 +1000
> > Nicholas Piggin wrote:
> >
> > > On Fri, 19 Aug 2016 10:37:00 +0200
> > > Michal Marek wrote:
> > >
> > > > On 2016-08-
On Mon, 22 Aug 2016 20:47:58 +1000
Nicholas Piggin wrote:
> On Fri, 19 Aug 2016 20:44:55 +1000
> Nicholas Piggin wrote:
>
> > On Fri, 19 Aug 2016 10:37:00 +0200
> > Michal Marek wrote:
> >
> > > On 2016-08-19 07:09, Stephen Rothwell wrote:
>
> [snip]
>
> > > >
> > > > I may be missin
On Fri, 19 Aug 2016 20:44:55 +1000
Nicholas Piggin wrote:
> On Fri, 19 Aug 2016 10:37:00 +0200
> Michal Marek wrote:
>
> > On 2016-08-19 07:09, Stephen Rothwell wrote:
[snip]
> > >
> > > I may be missing something, but genksyms generates the crc's off the
> > > preprocessed C source code a
On Fri, 19 Aug 2016 10:37:00 +0200
Michal Marek wrote:
> On 2016-08-19 07:09, Stephen Rothwell wrote:
> > Hi Nick,
> >
> > On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
> > wrote:
> >>
> >> On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin
> >> wrote:
> >>>
> >>> On Wed, 17 Aug 20
On 2016-08-19 07:09, Stephen Rothwell wrote:
> Hi Nick,
>
> On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
> wrote:
>>
>> On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin wrote:
>>>
>>> On Wed, 17 Aug 2016 14:59:59 +0200
>>> Michal Marek wrote:
>>>
On 2016-08-17 03:44, Stephen R
On Fri, 19 Aug 2016 15:09:14 +1000
Stephen Rothwell wrote:
> Hi Nick,
>
> On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
> wrote:
> >
> > On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin
> > wrote:
> > >
> > > On Wed, 17 Aug 2016 14:59:59 +0200
> > > Michal Marek wrote:
> > >
Hi Nick,
On Fri, 19 Aug 2016 13:38:54 +1000 Stephen Rothwell
wrote:
>
> On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin wrote:
> >
> > On Wed, 17 Aug 2016 14:59:59 +0200
> > Michal Marek wrote:
> >
> > > On 2016-08-17 03:44, Stephen Rothwell wrote:
> > > >
> > > > After merging the
Hi Nick,
On Thu, 18 Aug 2016 11:09:48 +1000 Nicholas Piggin wrote:
>
> On Wed, 17 Aug 2016 14:59:59 +0200
> Michal Marek wrote:
>
> > On 2016-08-17 03:44, Stephen Rothwell wrote:
> > >
> > > After merging the kbuild tree, today's linux-next build (powerpc
> > > ppc64_defconfig) produced thes
On Wed, 17 Aug 2016 14:59:59 +0200
Michal Marek wrote:
> On 2016-08-17 03:44, Stephen Rothwell wrote:
> > Hi Michal,
> >
> > After merging the kbuild tree, today's linux-next build (powerpc
> > ppc64_defconfig) produced these warnings:
> >
> > WARNING: 25 bad relocations
> > c0cf2570 R_
On 2016-08-17 03:44, Stephen Rothwell wrote:
> Hi Michal,
>
> After merging the kbuild tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> WARNING: 25 bad relocations
> c0cf2570 R_PPC64_ADDR64__crc___arch_hweight16
[...]
> Introduced by commit
>
>
I thought it had been...? Need to investigate (as baby permits...)
Stephen Rothwell wrote:
>Hi again,
>
>On Thu, 22 Dec 2011 16:33:04 +1100 Stephen Rothwell
> wrote:
>>
>> On Wed, 14 Dec 2011 08:47:01 -0800 "H. Peter Anvin"
>wrote:
>> >
>> > On 12/14/2011 08:32 AM, Steven Rostedt wrote:
>> > >
Hi again,
On Thu, 22 Dec 2011 16:33:04 +1100 Stephen Rothwell
wrote:
>
> On Wed, 14 Dec 2011 08:47:01 -0800 "H. Peter Anvin" wrote:
> >
> > On 12/14/2011 08:32 AM, Steven Rostedt wrote:
> > > On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote:
> > >
> > >> Maybe caused by commit d5e553d
Hi Peter,
On Wed, 14 Dec 2011 08:47:01 -0800 "H. Peter Anvin" wrote:
>
> On 12/14/2011 08:32 AM, Steven Rostedt wrote:
> > On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote:
> >
> >> Maybe caused by commit d5e553d6e0a4 ("trace: Include
> >> in trace_syscalls.c") from the tip tree. Thes
On Tue, Dec 20, 2011 at 7:13 PM, Stephen Rothwell wrote:
> Hi Josh,
>
> After merging the 4xx tree, today's linux-next build (powerpc ppc64_defconfig)
> produced these warnings:
>
> WARN: Uncompressed kernel (size 0xe32858) overlaps the address of the
> wrapper()
> WARN: Fixing the link_address o
On 12/14/2011 08:32 AM, Steven Rostedt wrote:
> On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote:
>
>> Maybe caused by commit d5e553d6e0a4 ("trace: Include
>> in trace_syscalls.c") from the tip tree. These warnings may have been
>> here for a while as it is hard to catch the new ones am
On Wed, 2011-12-14 at 18:15 +1100, Stephen Rothwell wrote:
> Maybe caused by commit d5e553d6e0a4 ("trace: Include
> in trace_syscalls.c") from the tip tree. These warnings may have been
> here for a while as it is hard to catch the new ones among the flood.
>
hpa,
Was this change only needed
* Stephen Rothwell wrote:
> Hi Yinghai,
>
> On Tue, 14 Sep 2010 16:00:06 -0700 Yinghai Lu wrote:
> >
> > Also, we may need to remove all extern and __init and __initdata etc in .h
> > files.
> >
> > please check
> >
> > [PATCH -v3] memblock: Fix section mismatch warning
> >
> > Use __init_
Hi Yinghai,
On Tue, 14 Sep 2010 16:00:06 -0700 Yinghai Lu wrote:
>
> Also, we may need to remove all extern and __init and __initdata etc in .h
> files.
>
> please check
>
> [PATCH -v3] memblock: Fix section mismatch warning
>
> Use __init_memblock to replace __init, and remove __init in memb
Hi Yinghai,
On Tue, 14 Sep 2010 18:33:34 -0700 Yinghai Lu wrote:
>
> On 09/14/2010 05:29 PM, Stephen Rothwell wrote:
> >
> > Do not remove the "extern" key word.
>
> why? you got another warning?
It is normal C coding practice to mark declarations in header files with
extern. It probably does
On 09/14/2010 05:29 PM, Stephen Rothwell wrote:
> Hi Yinghai,
>
> On Tue, 14 Sep 2010 16:00:06 -0700 Yinghai Lu wrote:
>>
>> Also, we may need to remove all extern and __init and __initdata etc in .h
>> files.
>
> Do not remove the "extern" key word.
>
why? you got another warning?
Yinghai
_
Hi Yinghai,
On Tue, 14 Sep 2010 16:00:06 -0700 Yinghai Lu wrote:
>
> Also, we may need to remove all extern and __init and __initdata etc in .h
> files.
Do not remove the "extern" key word.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
On 09/13/2010 09:50 PM, Stephen Rothwell wrote:
> Hi Yinghai,
>
> On Mon, 13 Sep 2010 01:24:20 -0700 Yinghai Lu wrote:
>>
>> On 09/12/2010 09:39 PM, Stephen Rothwell wrote:
>>>
>>> Your patch fixes some of the warnings, but still leaves these for a
>>> powerpc allnoconfig build:
>>>
>>> WARNING:
Hi Yinghai,
On Mon, 13 Sep 2010 01:24:20 -0700 Yinghai Lu wrote:
>
> On 09/12/2010 09:39 PM, Stephen Rothwell wrote:
> >
> > Your patch fixes some of the warnings, but still leaves these for a
> > powerpc allnoconfig build:
> >
> > WARNING: mm/built-in.o(.text+0x25d80): Section mismatch in refe
On 09/12/2010 09:39 PM, Stephen Rothwell wrote:
>
> Your patch fixes some of the warnings, but still leaves these for a
> powerpc allnoconfig build:
>
> WARNING: mm/built-in.o(.text+0x25d80): Section mismatch in reference from the
> function memblock_double_array() to the function .init.text:me
On 09/12/2010 08:27 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the scsi-post-merge tree, today's linux-next build (powerpc
> allnoconfig, i386 defconfig and others) produced these warnings (I build
> with CONFIG_DEBUG_SECTION_MISMATCH=y):
>
> WARNING: mm/built-in.o(.text+0x25910): Se
Hi Yinghai,
On Sun, 12 Sep 2010 21:14:15 -0700 Yinghai Lu wrote:
>
> please check it, and it should get into core/memblock branch.
>
> Thanks
>
> Yinghai
>
> [PATCH] memblock: Fix section mismatch warning
>
> for arches that use memblock other than x86
>
> Reported-by: Stephen Rothwell
> Si
54 matches
Mail list logo
