From: Chris Down <chris@chrisdown.name>
To: Amir Goldstein <amir73il@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Matthew Wilcox <willy@infradead.org>,
Jeff Layton <jlayton@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-team@fb.com
Subject: Re: [PATCH v3 1/2] tmpfs: Add per-superblock i_ino support
Date: Sun, 5 Jan 2020 11:28:51 +0000 [thread overview]
Message-ID: <20200105112851.GA243208@chrisdown.name> (raw)
In-Reply-To: <CAOQ4uxjZUYNjBZKU85TMCjtBf9ear7s4yxYSZcBX6rTZoYK-Hg@mail.gmail.com>
Amir Goldstein writes:
>Some nits. When fixed you may add:
>Reviewed-by: Amir Goldstein <amir73il@gmail.com>
Thanks! I'll fix these and comments on the other patches and send v4 here and
with linux-mm/tmpfs maintainer on cc. :-)
next prev parent reply other threads:[~2020-01-05 11:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 17:30 [PATCH v3 0/2] fs: inode: shmem: Reduce risk of inum overflow Chris Down
2020-01-03 17:30 ` [PATCH v3 1/2] tmpfs: Add per-superblock i_ino support Chris Down
2020-01-04 19:09 ` Amir Goldstein
2020-01-05 11:28 ` Chris Down [this message]
2020-01-03 17:30 ` [PATCH v3 2/2] tmpfs: Support 64-bit inums per-sb Chris Down
2020-01-04 19:15 ` Amir Goldstein
2020-01-04 21:16 ` [PATCH v3 0/2] fs: inode: shmem: Reduce risk of inum overflow Amir Goldstein
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=20200105112851.GA243208@chrisdown.name \
--to=chris@chrisdown.name \
--cc=amir73il@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=jlayton@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).