From: Mike Snitzer via Bugspray Bot <bugbot@kernel.org>
To: cel@kernel.org, linux-nfs@vger.kernel.org, anna@kernel.org,
trondmy@kernel.org, jlayton@kernel.org
Subject: Re: link error while compiling localio.c
Date: Tue, 22 Oct 2024 14:15:09 +0000 [thread overview]
Message-ID: <20241022-b219370c6-d93cfd00e8a0@bugzilla.kernel.org> (raw)
In-Reply-To: <20241022-b219370c5-c7de7745e4a0@bugzilla.kernel.org>
Mike Snitzer writes via Kernel.org Bugzilla:
(In reply to Mike Snitzer from comment #5)
> This was fixed via v6.12-rc3 commit 009b15b57485 ("nfs_common: fix
> Kconfig for NFS_COMMON_LOCALIO_SUPPORT")
>
> In the provided kernel config:
>
> CONFIG_NFS_FS=m
> CONFIG_NFSD_V4=y
> CONFIG_NFS_COMMON=y
> CONFIG_NFS_COMMON_LOCALIO_SUPPORT=m
> CONFIG_NFS_LOCALIO=y
>
> My Kconfig fix will result in CONFIG_NFS_LOCALIO=m so that the symbols
> are available to the nfs.ko kernel module.
Sorry, to be clear, the fix results in:
CONFIG_NFS_FS=m
CONFIG_NFSD=y
CONFIG_NFSD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_NFS_COMMON_LOCALIO_SUPPORT=y
CONFIG_NFS_LOCALIO=y
View: https://bugzilla.kernel.org/show_bug.cgi?id=219370#c6
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
prev parent reply other threads:[~2024-10-22 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 7:35 link error while compiling localio.c Janpieter Sollie via Bugspray Bot
2024-10-10 7:35 ` Janpieter Sollie via Bugspray Bot
2024-10-10 8:05 ` Janpieter Sollie via Bugspray Bot
2024-10-10 10:55 ` The Linux kernel's regression tracker (Thorsten Leemhuis) via Bugspray Bot
2024-10-22 10:40 ` The Linux kernel's regression tracker (Thorsten Leemhuis) via Bugspray Bot
2024-10-22 13:57 ` Mike Snitzer
2024-10-22 14:00 ` Mike Snitzer via Bugspray Bot
2024-10-22 14:15 ` Mike Snitzer via Bugspray Bot [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=20241022-b219370c6-d93cfd00e8a0@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.