Linux io-uring development
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: Re: [PATCH liburing] examples/zcrx: don't forget to sync dmabuf
Date: Fri, 16 Oct 2026 17:47:46 +0100	[thread overview]
Message-ID: <059a4998-cbec-4727-8a22-21aa0f3e601d@gmail.com> (raw)
In-Reply-To: <f4a6b4f9-d3fc-4f36-8c85-ca99ae2ed0d8@kernel.dk>

On 10/16/26 17:38, Jens Axboe wrote:
> On 10/16/26 10:36 AM, Pavel Begunkov wrote:
>> On 10/16/26 17:29, Jens Axboe wrote:
>>> On 10/16/26 10:25 AM, Pavel Begunkov wrote:
>>>> dma-bufs are not always coherent and we need to sync it before
>>>> accessing. Use proper dma-buf API for that.
>>>
>>> Can we get a Fixes tag for this please? Other fixes from today
>>> lacked that as well, please always add fixes tags.
>>
>> There was no "fixes" today.
> 
> Sure let's argue that, I merged 4 fixes from you this morning. None of
> them had Fixes tags.

There is nothing to argue about, I doubt anyone would call a
tabulation change or adding a kerneldoc "a fix".

>> liburing fixes tags either, but if you want to put one:
>>
>> Fixes: 93d3a7a70b4a6 ("examples/zcrx: udmabuf backed areas")
> 
> Because it's always nice to have the reference, even if there are
> no stable trees or anything like that on the liburing side.

Sure

-- 
Pavel Begunkov


  reply	other threads:[~2026-10-16 16:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 16:25 [PATCH liburing] examples/zcrx: don't forget to sync dmabuf Pavel Begunkov
2026-10-16 16:29 ` Jens Axboe
2026-10-16 16:36   ` Pavel Begunkov
2026-10-16 16:38     ` Jens Axboe
2026-10-16 16:47       ` Pavel Begunkov [this message]
2026-10-16 16:57         ` Jens Axboe
2026-10-16 16:39 ` 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=059a4998-cbec-4727-8a22-21aa0f3e601d@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@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