[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <32or985-8s52-17pr-62qq-s1q3r13p12no@syhkavp.arg>
Date: Thu, 11 Mar 2021 20:19:20 -0500 (EST)
From: Nicolas Pitre <nico@...xnic.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
cc: Masahiro Yamada <masahiroy@...nel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Nathan Chancellor <nathan@...nel.org>,
Bernhard Rosenkränzer <bero@...dev.ch>,
Miguel Ojeda <ojeda@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Will Deacon <will@...nel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kbuild: collect minimum tool versions into
scripts/min-tool-version.sh
On Thu, 11 Mar 2021, Miguel Ojeda wrote:
> On Thu, Mar 11, 2021 at 10:47 AM Masahiro Yamada <masahiroy@...nel.org> wrote:
> >
> > +# When you raise the minimum version, please update
> > +# Documentation/process/changes.rst as well.
> > +min_gcc_version=4.9.0
> > +min_llvm_version=10.0.1
> > +min_icc_version=16.0.3 # temporary
> > +min_binutils_version=2.23.0
>
> +1 to creating a central place for all minimum versions.
>
> Acked-by: Miguel Ojeda <ojeda@...nel.org>
>
> I wonder if you considered creating a folder with files like
> `scripts/min_versions/gcc` containing the version string. That would
> make it easier for reading from other languages or even importing them
> dynamically into the documentation, thus removing even more
> duplication.
Alternatively, the documentation could be the actual reference and the
script would parse the documentation to get those values out.
Nicolas
Powered by blists - more mailing lists