linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Frank Li <Frank.Li@nxp.com>, Jon Mason <jdmason@kudzu.us>,
	Alexander Fomichev <a.fomichev@yadro.com>
Subject: Re: linux-next: Tree for Jun 21 (NTB: pci-epf-vntb and test/ntb_perf)
Date: Tue, 21 Jun 2022 09:58:40 -0700	[thread overview]
Message-ID: <835b844b-9d9d-615c-af11-44154c2a8102@infradead.org> (raw)
In-Reply-To: <20220621193512.56d203c9@canb.auug.org.au>

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



On 6/21/22 02:35, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20220620:
> 

(a) on x86_64 or i386:

ERROR: modpost: "ntb_db_event" [drivers/pci/endpoint/functions/pci-epf-vntb.ko] undefined!
ERROR: modpost: "ntb_link_event" [drivers/pci/endpoint/functions/pci-epf-vntb.ko] undefined!
ERROR: modpost: "ntb_register_device" [drivers/pci/endpoint/functions/pci-epf-vntb.ko] undefined!

Full x86_64 randconfig file is attached.

(b) on i386:

ERROR: modpost: "__umoddi3" [drivers/ntb/test/ntb_perf.ko] undefined!

Probably here:

		/* Avoid processor soft lock-ups */
		if (!(pthr->tries % RESCHEDULE_RATIO))
			schedule();

-- 
~Randy

[-- Attachment #2: config-r4098.gz --]
[-- Type: application/gzip, Size: 38826 bytes --]

      reply	other threads:[~2022-06-21 17:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  9:35 linux-next: Tree for Jun 21 Stephen Rothwell
2022-06-21 16:58 ` Randy Dunlap [this message]

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=835b844b-9d9d-615c-af11-44154c2a8102@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=Frank.Li@nxp.com \
    --cc=a.fomichev@yadro.com \
    --cc=jdmason@kudzu.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).