From: Pavel Begunkov <[email protected]>
To: Mark Harmstone <[email protected]>, [email protected]
Cc: [email protected]
Subject: Re: [PATCH] btrfs: add struct io_btrfs_cmd as type for io_uring_cmd_to_pdu()
Date: Thu, 31 Oct 2024 16:10:13 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 10/31/24 16:03, Mark Harmstone wrote:
> Add struct io_btrfs_cmd as a wrapper type for io_uring_cmd_to_pdu(),
> rather than using a raw pointer.
That looks better, thanks. I don't think your patches got
merged yet, so you'd need to send it together with the next
version of your patchset, or even better squash it into the
patch 5/5.
--
Pavel Begunkov
next prev parent reply other threads:[~2024-10-31 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 16:03 [PATCH] btrfs: add struct io_btrfs_cmd as type for io_uring_cmd_to_pdu() Mark Harmstone
2024-10-31 16:10 ` Pavel Begunkov [this message]
[not found] <[email protected]>
2024-10-31 16:23 ` Mark Harmstone
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] \
[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