From: Pavel Begunkov <[email protected]>
To: Stefan Metzmacher <[email protected]>, [email protected]
Subject: Re: [PATCH 1/2] io_uring: remove structures from include/linux/io_uring.h
Date: Mon, 15 Mar 2021 11:02:00 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 14/03/2021 17:14, Stefan Metzmacher wrote:
> Hi Pavel,
>
>> Both patches are really nice. However, 1/2 doesn't apply
>> and looks it needs small stylistic changes, see nits below
>
> It seems the mails got corrupted, I played with git imap-send... :-(
>
> Here a branch with the patches:
> https://git.samba.org/?p=metze/linux/wip.git;a=shortlog;h=refs/heads/io_uring-5.12
>
> Should I resend them once I fixed my mail setup?
Who knows. Jens, do you want to take it for 5.12?
I just recently converted tctx->last from file* to ctx* and had to
gaze enough to not screw, in this light 2/2 looks good from the
safety perspective.
--
Pavel Begunkov
next prev parent reply other threads:[~2021-03-15 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
2021-03-14 11:15 ` [PATCH 1/2] io_uring: remove structures from include/linux/io_uring.h Stefan Metzmacher
2021-03-14 11:50 ` Pavel Begunkov
2021-03-14 17:14 ` Stefan Metzmacher
2021-03-15 11:02 ` Pavel Begunkov [this message]
2021-03-17 22:44 ` Jens Axboe
2021-03-15 11:56 ` [PATCH v2 0/2] Some header cleanups Stefan Metzmacher
2021-03-15 11:56 ` [PATCH v2 1/2] io_uring: remove structures from include/linux/io_uring.h Stefan Metzmacher
2021-03-15 11:56 ` [PATCH v2 2/2] io_uring: use typesafe pointers in io_uring_task Stefan Metzmacher
2021-03-17 22:45 ` [PATCH v2 0/2] Some header cleanups Jens Axboe
2021-03-14 11:15 ` [PATCH 2/2] io_uring: use typesafe pointers in io_uring_task Stefan Metzmacher
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