From: Qiliang Yuan <realwujing@gmail.com>
To: brauner@kernel.org
Cc: jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, realwujing@gmail.com,
viro@zeniv.linux.org.uk, yuanql9@chinatelecom.cn
Subject: Re: [PATCH v2] fs/file: optimize close_range() complexity from O(N) to O(Sparse)
Date: Mon, 26 Jan 2026 22:03:02 -0500 [thread overview]
Message-ID: <20260127030316.1189655-1-realwujing@gmail.com> (raw)
In-Reply-To: <20260123-wollust-vagabunden-af9d9bff4c4a@brauner>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 868 bytes --]
Hi Christian,
Thanks for your feedback and for applying this patch to the vfs-7.0.misc branch!
On Fri, Jan 23, 2026 at 3:38 PM Christian Brauner <brauner@kernel.org> wrote:
> Applied to the vfs-7.0.misc branch of the vfs/vfs.git tree.
> Patches in the vfs-7.0.misc branch should appear in linux-next soon.
>
> [1/1] fs/file: optimize close_range() complexity from O(N) to O(Sparse)
> https://git.kernel.org/vfs/vfs/c/fc94368bcee5
I tried to locate the commit in vfs/vfs-7.0.misc (and also searched by subject),
but I couldn’t find it yet.
Subject:
fs/file: optimize close_range() complexity from O(N) to O(Sparse)
Is the patch still in your local queue / pending push, or did it land with a
different commit hash after a rebase?
Just wanted to double-check the current status.
Thanks again for the review and for taking the patch.
Best regards,
Qiliang
next prev parent reply other threads:[~2026-01-27 3:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 16:35 [PATCH] " Qiliang Yuan
2026-01-22 17:14 ` Al Viro
2026-01-23 8:12 ` [PATCH v2] " Qiliang Yuan
2026-01-23 11:23 ` Jan Kara
2026-01-23 14:38 ` Christian Brauner
2026-01-27 3:03 ` Qiliang Yuan [this message]
2026-02-18 1:34 ` Eric Biggers
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=20260127030316.1189655-1-realwujing@gmail.com \
--to=realwujing@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yuanql9@chinatelecom.cn \
/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
Powered by JetHome