From: Jens Axboe <axboe@kernel.dk>
To: Yi Zhang <yi.zhang@redhat.com>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: [bug report] compiling error with latest linux-block/for-next
Date: Wed, 27 Jul 2022 09:21:45 -0600 [thread overview]
Message-ID: <41868484-07cd-2408-41c9-d48953b7a1af@kernel.dk> (raw)
In-Reply-To: <CAHj4cs8HjT6T8VCZtWzB1DzqHqcqex+bV6vdh2MdVwqNP9GH=A@mail.gmail.com>
On 7/27/22 9:18 AM, Yi Zhang wrote:
> Hello
> I found below compiling error[2] on latest linux-block/for-next[1],
> pls check it.
>
> [1]
> b8b914c06a6f (HEAD, origin/for-next) Merge branch
> 'for-5.20/drivers-post' into for-next
>
> [2]
> In file included from ./include/linux/export.h:33,
> from ./include/linux/linkage.h:7,
> from ./include/linux/kernel.h:17,
> from io_uring/notif.c:1:
> io_uring/notif.c: In function ?io_alloc_notif?:
> io_uring/notif.c:52:23: error: implicit declaration of function
> ?io_alloc_req_refill?; did you mean ?io_rsrc_refs_refill??
> [-Werror=implicit-function-declaration]
> 52 | if (unlikely(!io_alloc_req_refill(ctx)))
> | ^~~~~~~~~~~~~~~~~~~
> ./include/linux/compiler.h:78:45: note: in definition of macro ?unlikely?
> 78 | # define unlikely(x) __builtin_expect(!!(x), 0)
> | ^
> CC kernel/trace/trace_seq.o
> CC drivers/mfd/stmpe.o
> io_uring/notif.c:54:17: error: implicit declaration of function
> ?io_alloc_req?; did you mean ?xa_alloc_irq??
> [-Werror=implicit-function-declaration]
> 54 | notif = io_alloc_req(ctx);
> | ^~~~~~~~~~~~
> | xa_alloc_irq
> io_uring/notif.c:54:15: warning: assignment to ?struct io_kiocb *?
> from ?int? makes pointer from integer without a cast
> [-Wint-conversion]
> 54 | notif = io_alloc_req(ctx);
> | ^
This is fixed in the current tree.
--
Jens Axboe
prev parent reply other threads:[~2022-07-27 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 15:18 [bug report] compiling error with latest linux-block/for-next Yi Zhang
2022-07-27 15:21 ` Jens Axboe [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=41868484-07cd-2408-41c9-d48953b7a1af@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=yi.zhang@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.