From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] vfs: get_next_ino(), never inum=0
Date: Mon, 18 Aug 2014 15:21:06 -0300 [thread overview]
Message-ID: <20140818182106.GF23098@localhost.localdomain> (raw)
In-Reply-To: <1398786301-11484-1-git-send-email-hooanon05g@gmail.com>
This V2 looks very reasonable, and fix the problem with files with inode=0 on
tmpfs which I tested here, so, consider it
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
Cheers
--
Carlos
next prev parent reply other threads:[~2014-08-18 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 15:45 [PATCH] vfs: get_next_ino(), never inum=0 hooanon05g
2014-04-29 17:42 ` J. R. Okajima
2014-04-29 17:53 ` Christoph Hellwig
2014-04-30 4:08 ` J. R. Okajima
2014-04-30 22:56 ` Andreas Dilger
2014-05-10 3:18 ` J. R. Okajima
2014-08-18 18:21 ` Carlos Maiolino [this message]
2014-08-19 0:58 ` [PATCH v2] " J. R. Okajima
[not found] <'<CANn89i+PBEGp=9QGRioa7CUDZmApT-UNa=OJTdz4eu7AyO3Kbw@mail.gmail.com>
2014-05-28 14:06 ` J. R. Okajima
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=20140818182106.GF23098@localhost.localdomain \
--to=cmaiolino@redhat.com \
--cc=linux-fsdevel@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).