Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: Julian Braha <julianbraha@gmail.com>
To: mathieu.poirier@linaro.org, andersson@kernel.org, fabien.dessenne@st.com
Cc: ludovic.barre@st.com, loic.pallardy@st.com,
	arnaud.pouliquen@st.com, linux-kernel@vger.kernel.org,
	linux-remoteproc@vger.kernel.org,
	Julian Braha <julianbraha@gmail.com>
Subject: [PATCH v2] remoteproc: dead code cleanup in Kconfig for STM32_RPROC
Date: Fri, 17 Apr 2026 23:13:37 +0100	[thread overview]
Message-ID: <20260417221337.286313-1-julianbraha@gmail.com> (raw)

There is already an 'if REMOTEPROC' condition wrapping this config option,
making the 'depends on REMOTEPROC' statement a duplicate dependency
(dead code).

I propose leaving the outer 'if REMOTEPROC...endif' and removing the
individual 'depends on REMOTEPROC' statement.

This dead code was found by kconfirm, a static analysis tool for Kconfig.

Signed-off-by: Julian Braha <julianbraha@gmail.com>
---
v2: fix typo in commit message
Link to v1: https://lore.kernel.org/all/20260330224545.29769-1-julianbraha@gmail.com/
---
 drivers/remoteproc/Kconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig
index ee54436fea5a..c78e431b7b2d 100644
--- a/drivers/remoteproc/Kconfig
+++ b/drivers/remoteproc/Kconfig
@@ -316,7 +316,6 @@ config ST_SLIM_REMOTEPROC
 config STM32_RPROC
 	tristate "STM32 remoteproc support"
 	depends on ARCH_STM32 || COMPILE_TEST
-	depends on REMOTEPROC
 	select MAILBOX
 	help
 	  Say y here to support STM32 MCU processors via the
-- 
2.53.0


             reply	other threads:[~2026-04-17 22:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17 22:13 Julian Braha [this message]
2026-04-22 14:24 ` [PATCH v2] remoteproc: dead code cleanup in Kconfig for STM32_RPROC Mathieu Poirier

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=20260417221337.286313-1-julianbraha@gmail.com \
    --to=julianbraha@gmail.com \
    --cc=andersson@kernel.org \
    --cc=arnaud.pouliquen@st.com \
    --cc=fabien.dessenne@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=loic.pallardy@st.com \
    --cc=ludovic.barre@st.com \
    --cc=mathieu.poirier@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox