From: Shannon Nelson <shannon.nelson@amd•com>
To: Randy Dunlap <rdunlap@infradead•org>,
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>,
virtualization@lists•linux-foundation.org
Subject: Re: linux-next: Tree for Jul 6 [drivers/vdpa/pds/pds_vdpa.ko]
Date: Thu, 6 Jul 2023 15:26:05 -0700 [thread overview]
Message-ID: <b962951d-3372-b28a-8eb0-e0f36e58bd78@amd.com> (raw)
In-Reply-To: <fec68c3c-8249-7af4-5390-0495386a76f9@infradead.org>
On 7/6/23 2:07 PM, Randy Dunlap wrote:
>
> On 7/5/23 18:57, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do *not* add any v6.6 related stuff to your linux-next included
>> branches until after v6.5-rc1 has been released.
>>
>> Changes since 20230705:
>>
>
> On loongarch, when DEBUG_FS is not set:
>
> ERROR: modpost: "pds_vdpa_debugfs_del_vdpadev" [drivers/vdpa/pds/pds_vdpa.ko] undefined!
> ERROR: modpost: "pds_vdpa_debugfs_add_vdpadev" [drivers/vdpa/pds/pds_vdpa.ko] undefined!
> ERROR: modpost: "pds_vdpa_debugfs_reset_vdpadev" [drivers/vdpa/pds/pds_vdpa.ko] undefined!
> ERROR: modpost: "pds_vdpa_debugfs_create" [drivers/vdpa/pds/pds_vdpa.ko] undefined!
> ERROR: modpost: "pds_vdpa_debugfs_add_ident" [drivers/vdpa/pds/pds_vdpa.ko] undefined!
> ERROR: modpost: "pds_vdpa_debugfs_destroy" [drivers/vdpa/pds/pds_vdpa.ko] undefined!
> ERROR: modpost: "pds_vdpa_debugfs_add_pcidev" [drivers/vdpa/pds/pds_vdpa.ko] undefined!
Yikes - sorry, will follow up shortly.
sln
>
>
>
> Full randconfig file is attached.
>
> --
> ~Randy
next prev parent reply other threads:[~2023-07-06 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 1:57 linux-next: Tree for Jul 6 Stephen Rothwell
2023-07-06 21:07 ` linux-next: Tree for Jul 6 [drivers/vdpa/pds/pds_vdpa.ko] Randy Dunlap
2023-07-06 22:26 ` Shannon Nelson [this message]
2023-07-06 21:27 ` linux-next: Tree for Jul 6 (arch/riscv/) Randy Dunlap
2023-07-06 21:32 ` Palmer Dabbelt
2023-07-06 21:36 ` Randy Dunlap
2023-07-06 21:46 ` Palmer Dabbelt
2023-07-06 23:40 ` Randy Dunlap
2023-07-07 5:47 ` Palmer Dabbelt
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=b962951d-3372-b28a-8eb0-e0f36e58bd78@amd.com \
--to=shannon.nelson@amd$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=virtualization@lists$(echo .)linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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