public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Stefan Roesch <shr@devkernel.io>,
	Facebook Kernel Team <kernel-team@fb.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	Olivier Langlois <olivier@trillion01.com>,
	netdev Mailing List <netdev@vger.kernel.org>,
	io-uring Mailing List <io-uring@vger.kernel.org>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [RFC PATCH v2 2/4] liburing: add documentation for new napi busy polling
Date: Tue, 8 Nov 2022 15:04:41 +0700	[thread overview]
Message-ID: <7a6b630e-5863-fa0e-8520-fe687271f809@gnuweeb.org> (raw)
In-Reply-To: <20221107175357.2733763-3-shr@devkernel.io>

On 11/8/22 12:53 AM, Stefan Roesch wrote:
> +.TH io_uring_register_napi_busy_poll_timeout 3 "November 1, 2022" "liburing-2.3" "liburing Manual"
[...]
> +.TH io_uring_unregister_napi_busy_poll_timeout 3 "November 1, 2022" "liburing-2.3" "liburing Manual"

liburing-2.3 has already been released. These two should go to liburing-2.4.

See:

    https://github.com/axboe/liburing/tags

for the liburing version list.

-- 
Ammar Faizi


  reply	other threads:[~2022-11-08  8:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 17:53 [RFC PATCH v2 0/4] liburing: add api for napi busy poll timeout Stefan Roesch
2022-11-07 17:53 ` [RFC PATCH v2 1/4] liburing: add api to set " Stefan Roesch
2022-11-08  7:14   ` Ammar Faizi
2022-11-07 17:53 ` [RFC PATCH v2 2/4] liburing: add documentation for new napi busy polling Stefan Roesch
2022-11-08  8:04   ` Ammar Faizi [this message]
2022-11-07 17:53 ` [RFC PATCH v2 3/4] liburing: add test programs for napi busy poll Stefan Roesch
2022-11-08  7:01   ` Ammar Faizi
2022-11-08  9:47     ` Ammar Faizi
2022-11-07 17:53 ` [RFC PATCH v2 4/4] liburing: update changelog with new feature Stefan Roesch

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=7a6b630e-5863-fa0e-8520-fe687271f809@gnuweeb.org \
    --to=ammarfaizi2@gnuweeb.org \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=kernel-team@fb.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olivier@trillion01.com \
    --cc=shr@devkernel.io \
    /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