From: "J. R. Okajima" <hooanon05g@gmail.com>
To: linux-fsdevel@vger.kernel.org, adilger@dilger.ca, hch@lst.de,
dchinner@redhat.com, viro@zeniv.linux.org.uk, jlbec@evilplan.org,
gregkh@linuxfoundation.org, hughd@google.com
Subject: Re: [RFC 3/3] uniqueness of inode number, configfs, debugfs, procfs, ramfs and tmpfs
Date: Thu, 22 May 2014 10:03:11 +0900 [thread overview]
Message-ID: <30078.1400720591@jrobl> (raw)
In-Reply-To: <1400698140-25853-4-git-send-email-hooanon05g@gmail.com>
hooanon05g@gmail.com:
> Turn the feature ON which was introduced by previous commit.
It was for ramfs and tmpfs only.
configfs, debugfs and procfs don't need this.
J. R. Okajima
next prev parent reply other threads:[~2014-05-22 1:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 18:48 [RFC 0/3] vfs: get_next_ino(), never inum=0 and uniqueness hooanon05g
2014-05-21 18:48 ` [RFC 1/3] vfs: get_next_ino(), never inum=0 hooanon05g
2014-05-28 4:28 ` Hugh Dickins
2014-05-28 5:53 ` Eric Dumazet
2014-05-21 18:48 ` [RFC 2/3] vfs: get_next_ino(), support for the uniqueness hooanon05g
2014-05-22 11:56 ` Jan Kara
2014-05-22 15:03 ` J. R. Okajima
2014-05-22 15:12 ` Jan Kara
2014-05-22 15:14 ` Christoph Hellwig
2014-05-22 16:06 ` Jan Kara
2014-05-29 15:46 ` [PATCH v2 1/2] tmpfs: manage the inode-number by IDR J. R. Okajima
2014-05-29 15:46 ` [PATCH v2 2/2] tmpfs: refine a file handle for NFS-exporting J. R. Okajima
2014-05-31 2:43 ` [PATCH v2 1/2] tmpfs: manage the inode-number by IDR J. R. Okajima
2014-06-01 16:18 ` [RFC PATCH v3 0/2] the uniquness of tmpfs inode-number J. R. Okajima
2014-06-01 16:18 ` [RFC PATCH v3 1/2] tmpfs: manage the inode-number by IDR, signed int inum J. R. Okajima
2014-06-03 9:04 ` Jan Kara
2014-06-03 14:36 ` J. R. Okajima
2014-06-05 12:27 ` [RFC PATCH v4 0/2] tmpfs: manage the inode-number by IDR (performance measure) J. R. Okajima
2014-06-05 12:27 ` [RFC PATCH v4 1/2] tmpfs: manage the inode-number by IDR, signed int inum J. R. Okajima
2014-06-05 12:27 ` [RFC PATCH v4 2/2] tmpfs: refine a file handle for NFS-exporting J. R. Okajima
2014-06-01 16:18 ` [RFC PATCH v3 " J. R. Okajima
2014-05-21 18:49 ` [RFC 3/3] uniqueness of inode number, configfs, debugfs, procfs, ramfs and tmpfs hooanon05g
2014-05-22 1:03 ` J. R. Okajima [this message]
2014-05-22 11:53 ` Jan Kara
2014-05-22 14:58 ` J. R. Okajima
2014-05-22 15:09 ` Jan Kara
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=30078.1400720591@jrobl \
--to=hooanon05g@gmail.com \
--cc=adilger@dilger.ca \
--cc=dchinner@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=hughd@google.com \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@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).