From: Jeff Layton <jlayton@redhat.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)
Date: Fri, 15 Dec 2006 08:05:24 -0500 [thread overview]
Message-ID: <45829D94.1090304@redhat.com> (raw)
In-Reply-To: <457891E7.10902@redhat.com>
Jeff Layton wrote:
> Apologies for the long email, but I couldn't come up with a way to explain
> this in fewer words. Many filesystems that are part of the linux kernel
> have problems with how they have assign out i_ino values:
>
If there are no further comments/suggestions on this patchset, I'd like to
ask Andrew to add it to -mm soon and target getting it rolled into 2.6.21.
Once it's in -mm, I'll start posting more patches to convert the other
filesystems.
Andrew, are the patches I've already posted sufficient, or should I resend
the set?
Thanks,
Jeff
next prev parent reply other threads:[~2006-12-15 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 22:12 [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction) Jeff Layton
2006-12-15 13:05 ` Jeff Layton [this message]
2006-12-15 14:00 ` Jörn Engel
2006-12-15 15:01 ` Jeff Layton
2006-12-26 19:16 ` Jeff Layton
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=45829D94.1090304@redhat.com \
--to=jlayton@redhat.com \
--cc=akpm@osdl.org \
--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).