From: Akinobu Mita <akinobu.mita@gmail.com>
To: lkp@intel.com, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: akinobu.mita@gmail.com, axboe@kernel.dk,
oe-kbuild-all@lists.linux.dev, shinichiro.kawasaki@wdc.com,
chaitanyak@nvidia.com, akpm@linux-foundation.org,
hch@infradead.org
Subject: [PATCH -block] fault-inject: fix build error when FAULT_INJECTION_CONFIGFS=y and CONFIGFS_FS=m
Date: Sat, 15 Apr 2023 21:57:05 +0900 [thread overview]
Message-ID: <20230415125705.180426-1-akinobu.mita@gmail.com> (raw)
In-Reply-To: <202304150025.K0hczLR4-lkp@intel.com>
This fixes a build error when CONFIG_FAULT_INJECTION_CONFIGFS=y and
CONFIG_CONFIGFS_FS=m.
Since the fault-injection library cannot built as a module, avoid building
configfs as a module.
Reported-by: kernel test robot <lkp@intel.com>
Link: https://lore.kernel.org/oe-kbuild-all/202304150025.K0hczLR4-lkp@intel.com/
Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
---
lib/Kconfig.debug | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 6f64b49a2a8e..ce51d4dc6803 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1979,7 +1979,8 @@ config FAIL_SUNRPC
config FAULT_INJECTION_CONFIGFS
bool "Configfs interface for fault-injection capabilities"
- depends on FAULT_INJECTION && CONFIGFS_FS
+ depends on FAULT_INJECTION
+ select CONFIGFS_FS
help
This option allows configfs-based drivers to dynamically configure
fault-injection via configfs. Each parameter for driver-specific
--
2.34.1
next parent reply other threads:[~2023-04-15 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202304150025.K0hczLR4-lkp@intel.com>
2023-04-15 12:57 ` Akinobu Mita [this message]
2023-04-15 20:40 ` [PATCH -block] fault-inject: fix build error when FAULT_INJECTION_CONFIGFS=y and CONFIGFS_FS=m Jens Axboe
2023-04-16 9:53 ` Geert Uytterhoeven
2023-04-16 10:55 ` Arnd Bergmann
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=20230415125705.180426-1-akinobu.mita@gmail.com \
--to=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shinichiro.kawasaki@wdc.com \
/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).