From: Nathan Chancellor <nathan@kernel.org>
To: Ruihan Li <lrh2000@pku.edu.cn>
Cc: torvalds@linux-foundation.org, masahiroy@kernel.org,
arnd@arndb.de, bp@alien8.de, dave.hansen@linux.intel.com,
devel@acpica.org, lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, mingo@redhat.com, ndesaulniers@google.com,
ojeda@kernel.org, rafael@kernel.org, robert.moore@intel.com,
terrelln@fb.com, tglx@linutronix.de, trix@redhat.com,
x86@kernel.org
Subject: Re: [PATCH] scripts: Remove ICC-related dead code
Date: Mon, 24 Apr 2023 10:11:30 -0700 [thread overview]
Message-ID: <20230424171130.GA2606535@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20230424162110.11082-1-lrh2000@pku.edu.cn>
On Tue, Apr 25, 2023 at 12:21:10AM +0800, Ruihan Li wrote:
> Intel compiler support has already been completely removed in commit
> 95207db8166a ("Remove Intel compiler support"). However, it appears that
> there is still some ICC-related code in scripts/cc-version.sh. There is
> no harm in leaving the code as it is, but removing the dead code makes
> the codebase a bit cleaner.
>
> Hopefully all ICC-related stuff in the build scripts will be removed
> after this commit, given the grep output as below:
>
> (linux/scripts) $ grep -i -w -R 'icc'
> cc-version.sh:ICC)
> cc-version.sh: min_version=$($min_tool_version icc)
> dtc/include-prefixes/arm64/qcom/sm6350.dtsi:#include <dt-bindings/interconnect/qcom,icc.h>
>
> Fixes: 95207db8166a ("Remove Intel compiler support")
> Signed-off-by: Ruihan Li <lrh2000@pku.edu.cn>
Thanks for the patch. I am not sure this patch really needs a fixes tag,
as I do not really think dead code is a bug (and the commit message even
mentions this), but who cares I guess? :) cleanups are always nice.
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> ---
> scripts/cc-version.sh | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/scripts/cc-version.sh b/scripts/cc-version.sh
> index 0573c92e8..a7e28b6a5 100755
> --- a/scripts/cc-version.sh
> +++ b/scripts/cc-version.sh
> @@ -45,10 +45,6 @@ Clang)
> version=$2.$3.$4
> min_version=$($min_tool_version llvm)
> ;;
> -ICC)
> - version=$(($2 / 100)).$(($2 % 100)).$3
> - min_version=$($min_tool_version icc)
> - ;;
> *)
> echo "$orig_args: unknown C compiler" >&2
> exit 1
> --
> 2.40.0
>
next prev parent reply other threads:[~2023-04-24 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 18:23 [PATCH v3] Remove Intel compiler support Masahiro Yamada
2023-03-05 12:18 ` Masahiro Yamada
2023-03-05 18:52 ` Linus Torvalds
2023-04-24 16:21 ` [PATCH] scripts: Remove ICC-related dead code Ruihan Li
2023-04-24 16:27 ` Nick Desaulniers
2023-04-24 17:11 ` Nathan Chancellor [this message]
2023-04-24 17:27 ` Miguel Ojeda
2023-04-24 17:36 ` Linus Torvalds
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=20230424171130.GA2606535@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=devel@acpica.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lrh2000@pku.edu.cn \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=terrelln@fb.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=trix@redhat.com \
--cc=x86@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 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®