From: Dave Hansen <haveblue@us.ibm.com>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: linux-kernel@vger.kernel.org, hch@lst.de,
viro@zeniv.linux.org.uk, mm-commits@vger.kernel.org,
akpm@osdl.org
Subject: Re: - r-o-bind-mount-clean-up-ocfs2-nlink-handling.patch removed from -mm tree
Date: Wed, 13 Sep 2006 12:18:41 -0700 [thread overview]
Message-ID: <1158175121.9141.114.camel@localhost.localdomain> (raw)
In-Reply-To: <20060913191217.GJ8792@ca-server1.us.oracle.com>
On Wed, 2006-09-13 at 12:12 -0700, Mark Fasheh wrote:
> > Now that the vote call is gone, I don't think we even use future_nlink.
> > Can we just kill this entire section?
> Yeah, good catch. Lets try this one again...
Looks good to me. Thanks a bunch for updating this one.
Signed-off-by: Dave Hansen <haveblue@us.ibm.com>
-- Dave
prev parent reply other threads:[~2006-09-13 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609130506.k8D56U3m018878@shell0.pdx.osdl.net>
2006-09-13 18:27 ` - r-o-bind-mount-clean-up-ocfs2-nlink-handling.patch removed from -mm tree Mark Fasheh
2006-09-13 18:36 ` Dave Hansen
2006-09-13 19:12 ` Mark Fasheh
2006-09-13 19:18 ` Dave Hansen [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=1158175121.9141.114.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=mm-commits@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.