From: Pavel Begunkov <asml.silence@gmail.com>
To: leo.lilong@huaweicloud.com, axboe@kernel.dk
Cc: leo.lilong@huawei.com, yangerkun@huawei.com, io-uring@vger.kernel.org
Subject: Re: [PATCH] io_uring: update parameter name in io_pin_pages function declaration
Date: Fri, 25 Apr 2025 12:47:00 +0100 [thread overview]
Message-ID: <92a8fd11-ddd8-4ab3-a983-ff5c4cedefc2@gmail.com> (raw)
In-Reply-To: <20250425113241.2017508-1-leo.lilong@huaweicloud.com>
On 4/25/25 12:32, leo.lilong@huaweicloud.com wrote:
> From: Long Li <leo.lilong@huawei.com>
>
> Fix inconsistent first parameter name in io_pin_pages between declaration
> and implementation. Renamed `ubuf` to `uaddr` for better clarity.
>
> Fixes: 1943f96b3816 ("io_uring: unify io_pin_pages()")
I'm split on whether such patches make sense, slightly leaning
that they don't, but regardless, why is it a fix and which
problem exactly does it "fix"?
> Signed-off-by: Long Li <leo.lilong@huawei.com>
> ---
> io_uring/memmap.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/io_uring/memmap.h b/io_uring/memmap.h
> index dad0aa5b1b45..b9415a766c26 100644
> --- a/io_uring/memmap.h
> +++ b/io_uring/memmap.h
> @@ -4,7 +4,7 @@
> #define IORING_MAP_OFF_PARAM_REGION 0x20000000ULL
> #define IORING_MAP_OFF_ZCRX_REGION 0x30000000ULL
>
> -struct page **io_pin_pages(unsigned long ubuf, unsigned long len, int *npages);
> +struct page **io_pin_pages(unsigned long uaddr, unsigned long len, int *npages);
>
> #ifndef CONFIG_MMU
> unsigned int io_uring_nommu_mmap_capabilities(struct file *file);
--
Pavel Begunkov
next prev parent reply other threads:[~2025-04-25 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 11:32 [PATCH] io_uring: update parameter name in io_pin_pages function declaration leo.lilong
2025-04-25 11:47 ` Pavel Begunkov [this message]
2025-05-08 6:26 ` Long Li
-- strict thread matches above, loose matches on Subject: below --
2025-04-19 6:47 Long Li
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=92a8fd11-ddd8-4ab3-a983-ff5c4cedefc2@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=leo.lilong@huawei.com \
--cc=leo.lilong@huaweicloud.com \
--cc=yangerkun@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox