From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
linux-mips@vger.kernel.org,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
io-uring@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [next]: fs/io_uring.c:6171:10: error: implicit declaration of function 'io_sendmsg_prep_async'; did you mean 'io_req_prep_async'?
Date: Fri, 19 Feb 2021 09:18:59 -0700 [thread overview]
Message-ID: <a6c9a1f0-43a2-4c8d-a574-827e85e3c314@kernel.dk> (raw)
In-Reply-To: <87798def-0526-0a1e-6bcc-e5ee3970bd48@gmail.com>
On 2/19/21 9:10 AM, Pavel Begunkov wrote:
> On 19/02/2021 16:08, Naresh Kamboju wrote:
>> Linux next tag 20210219 arm and mips builds failed due to below error.
>>
>> Following build configs failed
>> arm (s3c6400_defconfig) with gcc-8
>> arm (s3c6400_defconfig) with gcc-9
>> arm (s3c6400_defconfig) with gcc-10
>>
>> mips (e55_defconfig) with gcc-8
>> mips (e55_defconfig) with gcc-9
>> mips (e55_defconfig) with gcc-10
>>
>> fs/io_uring.c:6171:10: error: implicit declaration of function
>> 'io_sendmsg_prep_async'; did you mean 'io_req_prep_async'?
>> [-Werror=implicit-function-declaration]
>> return io_sendmsg_prep_async(req);
>> ^~~~~~~~~~~~~~~~~~~~~
>> io_req_prep_async
>
> !CONFIG_NET, I guess. Thanks for letting know
Yep, I'm making a cleanup for that.
--
Jens Axboe
next prev parent reply other threads:[~2021-02-19 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 16:08 [next]: fs/io_uring.c:6171:10: error: implicit declaration of function 'io_sendmsg_prep_async'; did you mean 'io_req_prep_async'? Naresh Kamboju
2021-02-19 16:10 ` Pavel Begunkov
2021-02-19 16:18 ` Jens Axboe [this message]
2021-02-19 16:37 ` Jens Axboe
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=a6c9a1f0-43a2-4c8d-a574-827e85e3c314@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sfr@canb.auug.org.au \
/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).