From: Miklos Szeredi <miklos@szeredi.hu>
To: Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Dmitry Vyukov <dvyukov@google.com>,
linux-fsdevel@vger.kernel.org,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [RFC PATCH] vfs: fs{set,get}attr iops
Date: Tue, 24 Nov 2020 12:52:45 +0100 [thread overview]
Message-ID: <CAJfpegvb7U4wgYpe4KPtayM5kpdjX1SkhrgNLbxaRmm_Tn8noA@mail.gmail.com> (raw)
In-Reply-To: <20201124115004.GB22619@lst.de>
On Tue, Nov 24, 2020 at 12:50 PM Christoph Hellwig <hch@lst.de> wrote:
>
> Looks pretty neat from a quick look, but you probably want to split
> it into a patch or two adding the infrastructure and then one patch
> per file system to ease review and bisection.
Definitely. Just wanted to get this out to get early feedback.
Thanks,
Miklos
prev parent reply other threads:[~2020-11-24 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 14:12 [RFC PATCH] vfs: fs{set,get}attr iops Miklos Szeredi
2020-11-23 21:06 ` Andreas Dilger
2020-11-24 8:28 ` Miklos Szeredi
2020-11-24 11:50 ` Christoph Hellwig
2020-11-24 11:52 ` Miklos Szeredi [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=CAJfpegvb7U4wgYpe4KPtayM5kpdjX1SkhrgNLbxaRmm_Tn8noA@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=dvyukov@google.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).