public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fix for 6.4-rc5
Date: Fri, 2 Jun 2023 07:18:29 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

Just a single revert in here, removing the warning on the epoll ctl
opcode. We originally deprecated this a few releases ago, but I've since
had two people report that it's being used. Which isn't the biggest
deal, obviously this is why we out in the deprecation notice in the
first place, but it also means that we should just kill this warning
again and abandon the deprecation plans.

Since it's only a few handfuls of code to support epoll ctl, not worth
going any further with this imho.

Please pull!


The following changes since commit 533ab73f5b5c95dcb4152b52d5482abcc824c690:

  io_uring: unlock sqd->lock before sq thread release CPU (2023-05-25 09:30:13 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/io_uring-6.4-2023-06-02

for you to fetch changes up to 4ea0bf4b98d66a7a790abb285539f395596bae92:

  io_uring: undeprecate epoll_ctl support (2023-05-26 20:22:41 -0600)

----------------------------------------------------------------
io_uring-6.4-2023-06-02

----------------------------------------------------------------
Ben Noordhuis (1):
      io_uring: undeprecate epoll_ctl support

 io_uring/epoll.c | 4 ----
 1 file changed, 4 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2023-06-02 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 13:18 Jens Axboe [this message]
2023-06-02 17:41 ` [GIT PULL] io_uring fix for 6.4-rc5 pr-tracker-bot

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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