From: Zhang Qilong <[email protected]>
To: <[email protected]>, <[email protected]>, <[email protected]>
Cc: <[email protected]>
Subject: [PATCH -next] io_uring: Fix build error without CONFIG_EVENTFD
Date: Tue, 22 Nov 2022 20:02:43 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
If CONFIG_IO_URING=y, CONFIG_EVENTFD=n, bulding fails:
io_uring/io_uring.c: In function ‘io_eventfd_ops’:
io_uring/io_uring.c:498:3: error: implicit declaration of function ‘eventfd_signal_mask’; did you mean ‘eventfd_signal’? [-Werror=implicit-function-declaration]
eventfd_signal_mask(ev_fd->cq_ev_fd, 1, EPOLL_URING_WAKE);
This patch fixes that.
Fixes: 261187e66de3 ("io_uring: pass in EPOLL_URING_WAKE for eventfd signaling and wakeups")
Signed-off-by: Zhang Qilong <[email protected]>
---
include/linux/eventfd.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/include/linux/eventfd.h b/include/linux/eventfd.h
index e849329ce1a8..6c541c9a2478 100644
--- a/include/linux/eventfd.h
+++ b/include/linux/eventfd.h
@@ -67,6 +67,12 @@ static inline int eventfd_signal(struct eventfd_ctx *ctx, int n)
return -ENOSYS;
}
+static inline int eventfd_signal_mask(struct eventfd_ctx *ctx,
+ __u64 n, unsigned mask)
+{
+ return -ENOSYS;
+}
+
static inline void eventfd_ctx_put(struct eventfd_ctx *ctx)
{
--
2.25.1
next reply other threads:[~2022-11-22 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 12:02 Zhang Qilong [this message]
2022-11-22 13:10 ` [PATCH -next] io_uring: Fix build error without CONFIG_EVENTFD 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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