public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>
Cc: David Wei <dw@davidwei.uk>
Subject: Re: [PATCH liburing 0/5] zcrx example and other changes
Date: Wed, 16 Apr 2025 08:48:03 -0600	[thread overview]
Message-ID: <174481488391.330050.9226351914108896133.b4-ty@kernel.dk> (raw)
In-Reply-To: <cover.1744793980.git.asml.silence@gmail.com>


On Wed, 16 Apr 2025 10:01:12 +0100, Pavel Begunkov wrote:
> We need a simple example for zcrx to show case how the api works
> and how to use features. Patch 5 is a brushed up version of the
> zcrx selftest.
> 
> Apart from that update headers and use the kernel return zcrx id.
> 
> Pavel Begunkov (5):
>   Update io_uring.h for zcrx
>   tests/zcrx: rename a test
>   tests/zcrx: use returned right zcrx id
>   examples: add extra helpers
>   examples: add a zcrx example
> 
> [...]

Applied, thanks!

[1/5] Update io_uring.h for zcrx
      (no commit info)
[2/5] tests/zcrx: rename a test
      (no commit info)
[3/5] tests/zcrx: use returned right zcrx id
      (no commit info)
[4/5] examples: add extra helpers
      (no commit info)
[5/5] examples: add a zcrx example
      (no commit info)

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2025-04-16 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16  9:01 [PATCH liburing 0/5] zcrx example and other changes Pavel Begunkov
2025-04-16  9:01 ` [PATCH liburing 1/5] Update io_uring.h for zcrx Pavel Begunkov
2025-04-16  9:01 ` [PATCH liburing 2/5] tests/zcrx: rename a test Pavel Begunkov
2025-04-16  9:01 ` [PATCH liburing 3/5] tests/zcrx: use returned right zcrx id Pavel Begunkov
2025-04-16  9:01 ` [PATCH liburing 4/5] examples: add extra helpers Pavel Begunkov
2025-04-16  9:01 ` [PATCH liburing 5/5] examples: add a zcrx example Pavel Begunkov
2025-04-16 14:48 ` Jens Axboe [this message]

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=174481488391.330050.9226351914108896133.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=dw@davidwei.uk \
    --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