Hi all,
After merging the dmaengine tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
ld: warning: discarding dynamic section .glink
ld: warning: discarding dynamic section .plt
ld: linkage table error against `ioread64'
ld: stubs don't match calculated size
ld: can not build stubs: bad value
ld: fs/debugfs/file.o: in function `debugfs_print_regs':
file.c:(.text+0xee8): undefined reference to `ioread64be'
ld: file.c:(.text+0xf50): undefined reference to `ioread64'
Caused by commit
09289d0ad122 ("debugfs_create_regset32() support 8/16/64 bit width registers")
I have used the dmaengine tree from next-20230928 for today.
--
Cheers,
Stephen Rothwell
On 29-09-23, 13:13, Stephen Rothwell wrote:
> Hi all,
>
> After merging the dmaengine tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> ld: warning: discarding dynamic section .glink
> ld: warning: discarding dynamic section .plt
> ld: linkage table error against `ioread64'
> ld: stubs don't match calculated size
> ld: can not build stubs: bad value
> ld: fs/debugfs/file.o: in function `debugfs_print_regs':
> file.c:(.text+0xee8): undefined reference to `ioread64be'
> ld: file.c:(.text+0xf50): undefined reference to `ioread64'
>
> Caused by commit
>
> 09289d0ad122 ("debugfs_create_regset32() support 8/16/64 bit width registers")
>
> I have used the dmaengine tree from next-20230928 for today.
Thanks for report, I have dropped offending commits for now.
BR
--
~Vinod
> -----Original Message-----
> From: Vinod Koul <[email protected]>
> Sent: Monday, October 2, 2023 11:10 AM
> To: Stephen Rothwell <[email protected]>
> Cc: Frank Li <[email protected]>; Linux Kernel Mailing List <linux-
> [email protected]>; Linux Next Mailing List <[email protected]>
> Subject: [EXT] Re: linux-next: build failure after merge of the dmaengine tree
>
> Caution: This is an external email. Please take care when clicking links or
> opening attachments. When in doubt, report the message using the 'Report
> this email' button
>
>
> On 29-09-23, 13:13, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the dmaengine tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > ld: warning: discarding dynamic section .glink
> > ld: warning: discarding dynamic section .plt
> > ld: linkage table error against `ioread64'
> > ld: stubs don't match calculated size
> > ld: can not build stubs: bad value
> > ld: fs/debugfs/file.o: in function `debugfs_print_regs':
> > file.c:(.text+0xee8): undefined reference to `ioread64be'
> > ld: file.c:(.text+0xf50): undefined reference to `ioread64'
> >
> > Caused by commit
> >
> > 09289d0ad122 ("debugfs_create_regset32() support 8/16/64 bit width
> registers")
> >
> > I have used the dmaengine tree from next-20230928 for today.
>
> Thanks for report, I have dropped offending commits for now.
Fixed patch already post at
https://lore.kernel.org/dmaengine/[email protected]/T/#u
Frank
>
> BR
> --
> ~Vinod
Hello Frank,
On 02-10-23, 16:26, Frank Li wrote:
> > On 29-09-23, 13:13, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > After merging the dmaengine tree, today's linux-next build (powerpc
> > > ppc64_defconfig) failed like this:
> > >
> > > ld: warning: discarding dynamic section .glink
> > > ld: warning: discarding dynamic section .plt
> > > ld: linkage table error against `ioread64'
> > > ld: stubs don't match calculated size
> > > ld: can not build stubs: bad value
> > > ld: fs/debugfs/file.o: in function `debugfs_print_regs':
> > > file.c:(.text+0xee8): undefined reference to `ioread64be'
> > > ld: file.c:(.text+0xf50): undefined reference to `ioread64'
> > >
> > > Caused by commit
> > >
> > > 09289d0ad122 ("debugfs_create_regset32() support 8/16/64 bit width
> > registers")
> > >
> > > I have used the dmaengine tree from next-20230928 for today.
> >
> > Thanks for report, I have dropped offending commits for now.
>
> Fixed patch already post at
> https://lore.kernel.org/dmaengine/[email protected]/T/#u
I am not sure of this fix, someone has to pick this. let this get fixed
first and we can always pick back these patches.
My tree was broken meanwhile impacting others, so it was better to drop
for now.
Thanks for you understanding
--
~Vinod