From: lizetao <[email protected]>
To: Caleb Sander Mateos <[email protected]>
Cc: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
Jens Axboe <[email protected]>,
Pavel Begunkov <[email protected]>
Subject: RE: [PATCH] io_uring/rsrc: include io_uring_types.h in rsrc.h
Date: Mon, 3 Mar 2025 06:20:12 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Hi,
> -----Original Message-----
> From: Caleb Sander Mateos <[email protected]>
> Sent: Sunday, March 2, 2025 2:36 AM
> To: Jens Axboe <[email protected]>; Pavel Begunkov <[email protected]>
> Cc: Caleb Sander Mateos <[email protected]>; io-
> [email protected]; [email protected]
> Subject: [PATCH] io_uring/rsrc: include io_uring_types.h in rsrc.h
>
> io_uring/rsrc.h uses several types from include/linux/io_uring_types.h.
> Include io_uring_types.h explicitly in rsrc.h to avoid depending on users of
> rsrc.h including io_uring_types.h first.
>
> Signed-off-by: Caleb Sander Mateos <[email protected]>
> ---
> io_uring/rsrc.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/io_uring/rsrc.h b/io_uring/rsrc.h index 8f912aa6bcc9..f10a1252b3e9
> 100644
> --- a/io_uring/rsrc.h
> +++ b/io_uring/rsrc.h
> @@ -1,9 +1,10 @@
> // SPDX-License-Identifier: GPL-2.0
> #ifndef IOU_RSRC_H
> #define IOU_RSRC_H
>
> +#include <linux/io_uring_types.h>
> #include <linux/lockdep.h>
>
> enum {
> IORING_RSRC_FILE = 0,
> IORING_RSRC_BUFFER = 1,
> --
> 2.45.2
>
Reviewed-by: Li Zetao <[email protected]>
---
Li Zetao
next prev parent reply other threads:[~2025-03-03 6:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 18:36 [PATCH] io_uring/rsrc: include io_uring_types.h in rsrc.h Caleb Sander Mateos
2025-03-03 6:20 ` lizetao [this message]
2025-03-04 14:16 ` 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] \
[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