public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH 0/3] typesafety improvements on io_uring-6.0
Date: Thu, 11 Aug 2022 09:38:14 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Thu, 11 Aug 2022 09:11:13 +0200, Stefan Metzmacher wrote:
> with the split into individual files (which is gread)
> and the introduction of the generic struct io_cmd_data,
> we now have the risk do incompatible casting in
> io_kiocb_to_cmd().
> 
> My patches catch casting problems with BUILD_BUG_ON() now.
> While there I added missing BUILD_BUG_ON() checks
> for new io_uring_sqe fields.
> 
> [...]

Applied, thanks!

[1/3] io_uring: consistently make use of io_notif_to_data()
      commit: 3608c38ea378cb7bb2d43ebe43c468c7be58b83a
[2/3] io_uring: make io_kiocb_to_cmd() typesafe
      commit: 28789defa868b7b731ed73cfd7e0c0bfcd901de7
[3/3] io_uring: add missing BUILD_BUG_ON() checks for new io_uring_sqe fields
      commit: 4167efe6463b09505112b6dc2c30b8ac68fcf348

Best regards,
-- 
Jens Axboe



      parent reply	other threads:[~2022-08-11 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11  7:11 [PATCH 0/3] typesafety improvements on io_uring-6.0 Stefan Metzmacher
2022-08-11  7:11 ` [PATCH 1/3] io_uring: consistently make use of io_notif_to_data() Stefan Metzmacher
2022-08-11  7:11 ` [PATCH 2/3] io_uring: make io_kiocb_to_cmd() typesafe Stefan Metzmacher
2022-08-11  7:11 ` [PATCH 3/3] io_uring: add missing BUILD_BUG_ON() checks for new io_uring_sqe fields Stefan Metzmacher
2022-08-11 15:38 ` 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=166023229481.192529.11362562365058444938.b4-ty@kernel.dk \
    [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