From: Gourav Roy <gourav.bit@gmail.com>
To: axboe@kernel.dk
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
Gourav Roy <gourav.bit@gmail.com>
Subject: [PATCH] io-uring: fixed an int type code style issue
Date: Thu, 25 Dec 2025 21:16:16 -0800 [thread overview]
Message-ID: <20251226051616.124925-1-gourav.bit@gmail.com> (raw)
Fixed a code style issue to prefer 'unsigned int' over bare use of 'unsigned'.
Signed-off-by: Gourav Roy <gourav.bit@gmail.com>
---
io_uring/alloc_cache.c | 2 +-
io_uring/alloc_cache.h | 2 +-
io_uring/cancel.c | 2 +-
io_uring/eventfd.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/io_uring/alloc_cache.c b/io_uring/alloc_cache.c
index 58423888b736..9aee9f944d2c 100644
--- a/io_uring/alloc_cache.c
+++ b/io_uring/alloc_cache.c
@@ -19,7 +19,7 @@ void io_alloc_cache_free(struct io_alloc_cache *cache,
/* returns false if the cache was initialized properly */
bool io_alloc_cache_init(struct io_alloc_cache *cache,
- unsigned max_nr, unsigned int size,
+ unsigned int max_nr, unsigned int size,
unsigned int init_bytes)
{
cache->entries = kvmalloc_array(max_nr, sizeof(void *), GFP_KERNEL);
diff --git a/io_uring/alloc_cache.h b/io_uring/alloc_cache.h
index d33ce159ef33..8f70af6eb341 100644
--- a/io_uring/alloc_cache.h
+++ b/io_uring/alloc_cache.h
@@ -11,7 +11,7 @@
void io_alloc_cache_free(struct io_alloc_cache *cache,
void (*free)(const void *));
bool io_alloc_cache_init(struct io_alloc_cache *cache,
- unsigned max_nr, unsigned int size,
+ unsigned int max_nr, unsigned int size,
unsigned int init_bytes);
void *io_cache_alloc_new(struct io_alloc_cache *cache, gfp_t gfp);
diff --git a/io_uring/cancel.c b/io_uring/cancel.c
index ca12ac10c0ae..a9a674581871 100644
--- a/io_uring/cancel.c
+++ b/io_uring/cancel.c
@@ -104,7 +104,7 @@ static int io_async_cancel_one(struct io_uring_task *tctx,
}
int io_try_cancel(struct io_uring_task *tctx, struct io_cancel_data *cd,
- unsigned issue_flags)
+ unsigned int issue_flags)
{
struct io_ring_ctx *ctx = cd->ctx;
int ret;
diff --git a/io_uring/eventfd.c b/io_uring/eventfd.c
index 78f8ab7db104..ecf899a9c697 100644
--- a/io_uring/eventfd.c
+++ b/io_uring/eventfd.c
@@ -15,7 +15,7 @@ struct io_ev_fd {
struct eventfd_ctx *cq_ev_fd;
unsigned int eventfd_async;
/* protected by ->completion_lock */
- unsigned last_cq_tail;
+ unsigned int last_cq_tail;
refcount_t refs;
atomic_t ops;
struct rcu_head rcu;
--
2.51.0
reply other threads:[~2025-12-26 5:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251226051616.124925-1-gourav.bit@gmail.com \
--to=gourav.bit@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@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