No problem.
Documentation/process/changes.rst says the following:
You will need perl 5 and the following modules: ``Getopt::Long``,
``Getopt::Std``, ``File::Basename``, and ``File::Find`` to build the kernel.
We can assume perl is installed on the user's build machine.
--
Best Regards
Masahiro Yamada
+CC linux-crypto@vger.kernel.org
No functional change, though.
2018-03-23 22:04 GMT+09:00 Masahiro Yamada <yamada.masah...@socionext.com>:
> Clean up these patterns from the top Makefile to omit 'clean-files'
> in each Makefile.
>
> Signed-off-by: Masahiro Yamada <yamada.m
+CC linux-crypto@vger.kernel.org
No functional change, though.
(I fixed up the subject.)
2018-03-23 22:04 GMT+09:00 Masahiro Yamada <yamada.masah...@socionext.com>:
> Our convention is to distinguish file types by suffixes with a period
> as a separator.
>
> *-asn1.[ch] is a
+CC linux-crypto@vger.kernel.org
No functional change, though.
2018-03-23 22:04 GMT+09:00 Masahiro Yamada <yamada.masah...@socionext.com>:
> These are common patterns where source files are parsed by the
> asn1_compiler.
>
> Signed-off-by: Masahiro Yamada <yamada.m
hains with broken perl. The solution is minimally intrusive to
> make it easier to push into stable.
>
> Another report on a similar issue here: https://lkml.org/lkml/2018/3/8/1379
>
> Signed-off-by: Leonard Crestez <leonard.cres...@nxp.com>
> Cc: <sta...@vger.
ll cc-option, -mno-global-merge,)
> KBUILD_CFLAGS += $(call cc-option, -fcatch-undefined-behavior)
> +KBUILD_CFLAGS += $(call cc-option, -no-integrated-as)
> +KBUILD_AFLAGS += $(call cc-option, -no-integrated-as)
> else
>
> # These warnings generated too much noise in a regular build.
--
Best Regards
Masahiro Yamada
9624573/).
In a such case, we may end up with swapping the order,
but this should not happen quite often.
> On Wed, Apr 5, 2017 at 12:01 PM, Matthias Kaehlcke <m...@chromium.org> wrote:
>> Hi Masahiro,
>>
>> El Thu, Apr 06, 2017 at 03:08:26AM +0900 Masahiro Yamada ha dit:
>
