From: Dmitry Kadashev <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Linus Torvalds <[email protected]>,
Alexander Viro <[email protected]>,
Christian Brauner <[email protected]>,
Pavel Begunkov <[email protected]>,
linux-fsdevel <[email protected]>,
io-uring <[email protected]>
Subject: Re: [PATCH v9 00/11] io_uring: add mkdir and [sym]linkat support
Date: Fri, 13 Aug 2021 16:32:12 +0700 [thread overview]
Message-ID: <CAOKbgA5jHtR=tLAYS_rs77QppRm37HV1bqSLQEMv8GusQNDrAg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Fri, Jul 9, 2021 at 2:25 AM Jens Axboe <[email protected]> wrote:
>
> On 7/8/21 12:34 PM, Linus Torvalds wrote:
> > On Wed, Jul 7, 2021 at 11:35 PM Dmitry Kadashev <[email protected]> wrote:
> >>
> >> v9:
> >> - reorder commits to keep io_uring ones nicely grouped at the end
> >> - change 'fs:' to 'namei:' in related commit subjects, since this is
> >> what seems to be usually used in such cases
> >
> > Ok, ack from me on this series, and as far as I'm concerned it can go
> > through the io_uring branch.
>
> I'll queue it up in a separate branch. I'm assuming we're talking 5.15
> at this point.
Is this going to be merged into 5.15? I'm still working on the follow-up
patch (well, right at this moment I'm actually on vacation, but will be
working on it when I'm back), but hopefully it does not have to be
merged in the same merge window / version? Especially given the fact
that Al prefers it to be a bigger refactoring of the ESTALE retries
rather than just moving bits and pieces to helper functions to simplify
the flow, see here:
https://lore.kernel.org/io-uring/[email protected]/
--
Dmitry Kadashev
next prev parent reply other threads:[~2021-08-13 9:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 6:34 [PATCH v9 00/11] io_uring: add mkdir and [sym]linkat support Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 01/11] namei: ignore ERR/NULL names in putname() Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 02/11] namei: change filename_parentat() calling conventions Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 03/11] namei: make do_mkdirat() take struct filename Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 04/11] namei: make do_mknodat() " Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 05/11] namei: make do_symlinkat() " Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 06/11] namei: add getname_uflags() Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 07/11] namei: make do_linkat() take struct filename Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 08/11] namei: update do_*() helpers to return ints Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 09/11] io_uring: add support for IORING_OP_MKDIRAT Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 10/11] io_uring: add support for IORING_OP_SYMLINKAT Dmitry Kadashev
2021-07-08 6:34 ` [PATCH v9 11/11] io_uring: add support for IORING_OP_LINKAT Dmitry Kadashev
2021-07-08 18:34 ` [PATCH v9 00/11] io_uring: add mkdir and [sym]linkat support Linus Torvalds
2021-07-08 19:25 ` Jens Axboe
2021-08-13 9:32 ` Dmitry Kadashev [this message]
2021-08-13 14:12 ` Jens Axboe
2021-08-16 10:24 ` Dmitry Kadashev
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='CAOKbgA5jHtR=tLAYS_rs77QppRm37HV1bqSLQEMv8GusQNDrAg@mail.gmail.com' \
[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