From: Josua Mayer <josua@solid-run.com>
To: Peter Rosin <peda@axentia.se>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-kernel@vger.kernel.org, Josua Mayer <josua@solid-run.com>
Subject: [PATCH next] mux: fix build-error when mux-core is built as module
Date: Mon, 09 Feb 2026 13:24:31 +0200 [thread overview]
Message-ID: <20260209-rz-sdio-mux-fix-v1-1-8ea0da565b14@solid-run.com> (raw)
The mux core header file uses ifdef CONFIG_MULTIPLEXER to select between
helper function prototypes and static inline stubs.
This leads to build errors when CONFIG_MULTIPLEXER=m, because then
CONFIG_MULTIPLEXER_MODULE is defined instead.
Replace the ifdef with IS_ENABLED to catch both builtin and module
cases, and fix the build error in module case.
Fixes: ad314348ceb4 ("mux: Add helper functions for getting optional and selected mux-state")
Signed-off-by: Josua Mayer <josua@solid-run.com>
---
include/linux/mux/consumer.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/mux/consumer.h b/include/linux/mux/consumer.h
index 3ede55b907eb..a961861a503b 100644
--- a/include/linux/mux/consumer.h
+++ b/include/linux/mux/consumer.h
@@ -16,7 +16,7 @@ struct device;
struct mux_control;
struct mux_state;
-#ifdef CONFIG_MULTIPLEXER
+#if IS_ENABLED(CONFIG_MULTIPLEXER)
unsigned int mux_control_states(struct mux_control *mux);
int __must_check mux_control_select_delay(struct mux_control *mux,
---
base-commit: 13dc45d829d5ae06f6eee3fbd3cd1f6818c08e48
change-id: 20260209-rz-sdio-mux-fix-e8fa9c62ff95
Best regards,
--
Josua Mayer <josua@solid-run.com>
next reply other threads:[~2026-02-09 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 11:24 Josua Mayer [this message]
2026-02-10 13:36 ` Ulf Hansson
2026-02-10 13:45 ` Peter Rosin
2026-02-11 11:42 ` Ulf Hansson
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=20260209-rz-sdio-mux-fix-v1-1-8ea0da565b14@solid-run.com \
--to=josua@solid-run.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®