From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Sasha Levin <sashal@kernel.org>,
linux- stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org
Subject: Re: stable-rc 4.19: lib/vsprintf.c:1983:11: error: implicit declaration of function ‘error_string’ [-Werror=implicit-function-declaration] 1983 | return error_string(buf, end, "(einval)", spec);
Date: Mon, 18 May 2020 19:31:01 +0200 [thread overview]
Message-ID: <20200518173101.GA2394423@kroah.com> (raw)
In-Reply-To: <CA+G9fYtUOp8d1ktnp_-34AczAqR+eCj7UfD9u30hdYAey66syw@mail.gmail.com>
On Mon, May 18, 2020 at 10:49:08PM +0530, Naresh Kamboju wrote:
> stable-rc 4.19 build broken on arm64, arm, x86_64 and i386.
>
> # make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j16 ARCH=x86
> HOSTCC=gcc CC="sccache gcc" O=build
> 75 #
> 76 kernel/locking/rwsem.o: warning: objtool: up_read()+0x11: call
> without frame pointer save/setup
> 77 kernel/locking/rwsem.o: warning: objtool: up_write()+0x17: call
> without frame pointer save/setup
> 78 kernel/locking/rwsem.o: warning: objtool: downgrade_write()+0x25:
> call without frame pointer save/setup
> 79 ../drivers/crypto/ccp/sp-platform.c:37:34: warning: array
> ‘sp_of_match’ assumed to have one element
> 80 37 | static const struct of_device_id sp_of_match[];
> 81 | ^~~~~~~~~~~
> 82 ../lib/vsprintf.c: In function ‘pointer’:
> 83 ../lib/vsprintf.c:1983:11: error: implicit declaration of function
> ‘error_string’ [-Werror=implicit-function-declaration]
> 84 1983 | return error_string(buf, end, "(einval)", spec);
> 85 | ^~~~~~~~~~~~
> 86 ../lib/vsprintf.c:1983:11: warning: returning ‘int’ from a function
> with return type ‘char *’ makes pointer from integer without a cast
> [-Wint-conversion]
> 87 1983 | return error_string(buf, end, "(einval)", spec);
> 88 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 89 cc1: some warnings being treated as errors
>
> ref:
> https://gitlab.com/Linaro/lkft/kernel-runs/-/jobs/557410092
> https://gitlab.com/Linaro/lkft/kernel-runs/-/jobs/557410099
Should all now be fixed, sorry for the churn.
greg k-h
prev parent reply other threads:[~2020-05-18 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 17:19 stable-rc 4.19: lib/vsprintf.c:1983:11: error: implicit declaration of function ‘error_string’ [-Werror=implicit-function-declaration] 1983 | return error_string(buf, end, "(einval)", spec); Naresh Kamboju
2020-05-18 17:31 ` Greg Kroah-Hartman [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=20200518173101.GA2394423@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).