From: Al Viro <viro@zeniv.linux.org.uk>
To: Gou Hao <gouhao@uniontech.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
jiaofenfang@uniontech.com
Subject: Re: [PATCH] fs: remove fget_many and fput_many interface
Date: Mon, 1 Nov 2021 16:31:43 +0000 [thread overview]
Message-ID: <YYAWb5fg5uQQN5H9@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <20211101051931.21544-1-gouhao@uniontech.com>
On Mon, Nov 01, 2021 at 01:19:31PM +0800, Gou Hao wrote:
> From: gouhao <gouhao@uniontech.com>
>
> These two interface were added in 091141a42 commit,
> but now there is no place to call them.
Gladly. I'd add a reference to the commit that had removed the need
of that wart (62906e89e63b "io_uring: remove file batch-get optimisation")
to the commit message, but yes, that's something I'm very happy to apply.
prev parent reply other threads:[~2021-11-01 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 5:19 [PATCH] fs: remove fget_many and fput_many interface Gou Hao
2021-11-01 12:25 ` Matthew Wilcox
2021-11-01 16:31 ` Al Viro [this message]
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=YYAWb5fg5uQQN5H9@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=gouhao@uniontech.com \
--cc=jiaofenfang@uniontech.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).