From: David Miller <davem@davemloft.net>
To: masahiroy@kernel.org
Cc: linux-kbuild@vger.kernel.org, sparclinux@vger.kernel.org,
clang-built-linux@googlegroups.com, viro@zeniv.linux.org.uk,
ndesaulniers@google.com, ilie.halip@gmail.com,
natechancellor@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] sparc: revive __HAVE_ARCH_STRLEN for 32bit sparc
Date: Mon, 16 Mar 2020 17:48:36 -0700 (PDT) [thread overview]
Message-ID: <20200316.174836.1008034012256551916.davem@davemloft.net> (raw)
In-Reply-To: <20200311223725.27662-1-masahiroy@kernel.org>
From: Masahiro Yamada <masahiroy@kernel.org>
Date: Thu, 12 Mar 2020 07:37:24 +0900
> Prior to commit 70a6fcf3283a ("[sparc] unify 32bit and 64bit string.h"),
> __HAVE_ARCH_STRLEN was defined in both of string_32.h and string_64.h
>
> It did not unify __HAVE_ARCH_STRLEN, but deleted it from string_32.h
>
> This issue was reported by the kbuild test robot in the trial of
> forcible linking of $(lib-y) to vmlinux.
>
> Fixes: 70a6fcf3283a ("[sparc] unify 32bit and 64bit string.h")
> Reported-by: kbuild test robot <lkp@intel.com>
> Suggested-by: Nick Desaulniers <ndesaulniers@google.com>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Acked-by: David S. Miller <davem@davemloft.net>
prev parent reply other threads:[~2020-03-17 0:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 22:37 [PATCH v2 1/2] sparc: revive __HAVE_ARCH_STRLEN for 32bit sparc Masahiro Yamada
2020-03-11 22:37 ` [PATCH v2 2/2] kbuild: link lib-y objects to vmlinux forcibly when CONFIG_MODULES=y Masahiro Yamada
2020-03-12 4:30 ` kbuild test robot
2020-03-12 6:12 ` Masahiro Yamada
2020-03-12 8:39 ` Thomas Bogendoerfer
2020-03-19 15:48 ` Masahiro Yamada
2020-03-19 16:22 ` Thomas Bogendoerfer
2020-03-16 23:13 ` Nick Desaulniers
2020-03-16 23:18 ` Nick Desaulniers
2020-04-02 17:13 ` Masahiro Yamada
2020-03-12 1:50 ` [PATCH v2 1/2] sparc: revive __HAVE_ARCH_STRLEN for 32bit sparc Nick Desaulniers
2020-03-17 0:48 ` David Miller [this message]
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=20200316.174836.1008034012256551916.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=clang-built-linux@googlegroups.com \
--cc=ilie.halip@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=sparclinux@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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