From: Dave Chinner <david@fromorbit.com>
To: Sage Weil <sage@inktank.com>
Cc: viro@zeniv.linux.org.uk, "Yan, Zheng" <zheng.z.yan@intel.com>,
linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org,
greg@inktank.com
Subject: Re: [RESEND][PATCH] fs: remove dentry_lru_prune()
Date: Mon, 22 Apr 2013 17:56:23 +1000 [thread overview]
Message-ID: <20130422075623.GI13938@destitution> (raw)
In-Reply-To: <alpine.DEB.2.00.1304191343110.13036@cobra.newdream.net>
On Sun, Apr 21, 2013 at 01:34:02PM -0700, Sage Weil wrote:
> Al-
>
> As I mentioned LSF, since there are no other users except for ceph, it's
> probably easiest if this goes through my tree. Unless you expect
> conflicts with other vfs bits or want this to go through the vfs tree...
> Either way!
Sage, it'll probably conflict with the generic LRU rework, so there
might be some co-ordination needed there...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2013-04-22 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 6:13 [RESEND][PATCH] fs: remove dentry_lru_prune() Yan, Zheng
2013-04-16 14:59 ` Sage Weil
2013-04-21 20:34 ` Sage Weil
2013-04-22 7:56 ` Dave Chinner [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=20130422075623.GI13938@destitution \
--to=david@fromorbit.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sage@inktank.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zheng.z.yan@intel.com \
/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.