public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vinod Koul <vkoul@kernel.org>
Cc: Frank Li <Frank.Li@nxp.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the dmaengine tree
Date: Fri, 29 Sep 2023 13:13:24 +1000	[thread overview]
Message-ID: <20230929131324.6bb84292@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 711 bytes --]

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-09-29  3:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29  3:13 Stephen Rothwell [this message]
2023-10-02 16:09 ` linux-next: build failure after merge of the dmaengine tree Vinod Koul
2023-10-02 16:26   ` [EXT] " Frank Li
2023-10-04  7:18     ` Vinod Koul
  -- strict thread matches above, loose matches on Subject: below --
2023-10-10  3:54 Stephen Rothwell
2023-10-10  6:59 ` Vinod Koul
2023-10-11 13:41 ` Rob Herring
2023-10-12 12:30   ` Vinod Koul
2022-06-10  2:46 Stephen Rothwell
2022-06-10  4:32 ` Vinod Koul
2021-10-26  5:06 Stephen Rothwell
2021-10-26  5:07 ` Stephen Rothwell
2021-10-26  5:26 ` Vinod Koul

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=20230929131324.6bb84292@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Frank.Li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=vkoul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox