Linux io-uring development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Caleb Sander Mateos <csander@purestorage.com>, Yi Xie <xieyi@kylinos.cn>
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH] io_uring: parenthesize io_ring_head_to_buf() expansion
Date: Thu, 14 May 2026 08:25:21 -0600	[thread overview]
Message-ID: <49a10373-f2d8-4813-b9d6-25cd2a0f2fe6@kernel.dk> (raw)
In-Reply-To: <CADUfDZoYZ5hGejvoZrCzhef2LrB04cbDsdoe+jyGnhL6Pnn4FQ@mail.gmail.com>

On 5/14/26 8:22 AM, Caleb Sander Mateos wrote:
> On Thu, May 14, 2026 at 1:35?AM Yi Xie <xieyi@kylinos.cn> wrote:
>>
>> Wrap the io_ring_head_to_buf() macro value in an extra pair of parentheses
>> so it is safe when composed into larger expressions, and to satisfy
>> scripts/checkpatch.pl.
>>
>> Signed-off-by: Yi Xie <xieyi@kylinos.cn>
>> ---
>>  io_uring/kbuf.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
>> index 63061aa1cab9..dd54e43e9ddf 100644
>> --- a/io_uring/kbuf.c
>> +++ b/io_uring/kbuf.c
>> @@ -21,7 +21,7 @@
>>  #define MAX_BIDS_PER_BGID (1 << 16)
>>
>>  /* Mapped buffer ring, return io_uring_buf from head */
>> -#define io_ring_head_to_buf(br, head, mask)    &(br)->bufs[(head) & (mask)]
>> +#define io_ring_head_to_buf(br, head, mask)    (&(br)->bufs[(head) & (mask)])
> 
> Is there a reason this can't just be an inline function?

No reason at all. But also don't see a strong reason why it can't just
be a define. And generally I don't like cleanups like this, but this one
at least made sense to me.

-- 
Jens Axboe

  reply	other threads:[~2026-05-14 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14  8:34 [PATCH] io_uring: parenthesize io_ring_head_to_buf() expansion Yi Xie
2026-05-14 13:24 ` Jens Axboe
2026-05-14 14:22 ` Caleb Sander Mateos
2026-05-14 14:25   ` Jens Axboe [this message]
2026-05-14 14:43     ` Caleb Sander Mateos
2026-05-14 14:44       ` Jens Axboe
2026-05-14 14:58     ` Gabriel Krisman Bertazi
2026-05-14 15:02       ` 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 \
    --in-reply-to=49a10373-f2d8-4813-b9d6-25cd2a0f2fe6@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=csander@purestorage.com \
    --cc=io-uring@vger.kernel.org \
    --cc=xieyi@kylinos.cn \
    /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