From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: [PATCH 5/6] kconfig: remove unreachable printf()
Date: Sun, 3 Dec 2023 19:25:27 +0900 [thread overview]
Message-ID: <20231203102528.1913822-5-masahiroy@kernel.org> (raw)
In-Reply-To: <20231203102528.1913822-1-masahiroy@kernel.org>
Remove the unreachable code detected by clang.
$ make HOSTCC=clang HOSTCFLAGS=-Wunreachable-code defconfig
[ snip ]
scripts/kconfig/expr.c:1134:2: warning: code will never be executed [-Wunreachable-code]
printf("[%dgt%d?]", t1, t2);
^~~~~~
1 warning generated.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
---
scripts/kconfig/expr.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/kconfig/expr.c b/scripts/kconfig/expr.c
index 81ebf8108ca7..a290de36307b 100644
--- a/scripts/kconfig/expr.c
+++ b/scripts/kconfig/expr.c
@@ -1131,7 +1131,6 @@ static int expr_compare_type(enum expr_type t1, enum expr_type t2)
default:
return -1;
}
- printf("[%dgt%d?]", t1, t2);
return 0;
}
--
2.40.1
next prev parent reply other threads:[~2023-12-03 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 10:25 [PATCH 1/6] kconfig: factor out common code shared by mconf and nconf Masahiro Yamada
2023-12-03 10:25 ` [PATCH 2/6] kconfig: make menu_warn() static function Masahiro Yamada
2023-12-03 10:25 ` [PATCH 3/6] kconfig: squash menu_has_help() and menu_get_help() Masahiro Yamada
2023-12-03 10:25 ` [PATCH 4/6] kconfig: add include guard to lkc_proto.h Masahiro Yamada
2023-12-03 10:25 ` Masahiro Yamada [this message]
2023-12-03 10:25 ` [PATCH 6/6] kconfig: remove redundant NULL pointer check before free() Masahiro Yamada
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=20231203102528.1913822-5-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=trix@redhat.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®