From: Kanchan Joshi <[email protected]>
To: Jens Axboe <[email protected]>, Keith Busch <[email protected]>
Cc: Keith Busch <[email protected]>,
[email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected]
Subject: Re: [PATCHv5 0/4] block integrity: directly map user space addresses
Date: Sat, 2 Dec 2023 07:34:12 +0530 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 12/2/2023 7:01 AM, Jens Axboe wrote:
>> Jens already applied the latest series for the next merge. We can append
>> this or fold atop, or back it out and we can rework it for another
>> version. No rush; for your patch:
> I folded this into the original to avoid the breakage, even if it wasn't
> a huge concern for this particular issue. But it's close enough to
> merging, figured we may as well do that rather than have a fixup patch.
>
> Please check the end result, both for-next and for-6.8/block are updated
> now.
Looks good to me.
May not matter now, so a symbolic
Reviewed-by: Kanchan Joshi <[email protected]>
next prev parent reply other threads:[~2023-12-02 2:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231130215715epcas5p33208ca14e69a68402c04e5c743135e6c@epcas5p3.samsung.com>
2023-11-30 21:53 ` [PATCHv5 0/4] block integrity: directly map user space addresses Keith Busch
2023-11-30 21:53 ` [PATCHv5 1/4] block: bio-integrity: directly map user buffers Keith Busch
2023-11-30 21:53 ` [PATCHv5 2/4] nvme: use bio_integrity_map_user Keith Busch
2023-11-30 21:53 ` [PATCHv5 3/4] iouring: remove IORING_URING_CMD_POLLED Keith Busch
2023-11-30 21:53 ` [PATCHv5 4/4] io_uring: remove uring_cmd cookie Keith Busch
2023-11-30 23:09 ` [PATCHv5 0/4] block integrity: directly map user space addresses Jens Axboe
2023-12-01 10:43 ` Kanchan Joshi
2023-12-01 18:42 ` Keith Busch
2023-12-01 22:49 ` Keith Busch
2023-12-02 1:31 ` Jens Axboe
2023-12-02 2:04 ` Kanchan Joshi [this message]
2023-12-02 14:58 ` Jens Axboe
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] \
[email protected] \
[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