public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Add two VFS exports used by POHMELFS
Date: Wed, 14 Jan 2009 00:30:13 +0300	[thread overview]
Message-ID: <20090113213013.GA27227@ioremap.net> (raw)
In-Reply-To: <20090113165630.GA25450@kroah.com>

On Tue, Jan 13, 2009 at 08:56:30AM -0800, Greg KH (greg@kroah.com) wrote:
> > POHMELFS is a very high-performance parallel network filesystem with
> > coherent local cache of data and metadata. It entered maintenance mode
> > and is being prepared for the next submission cycle.
> > I decided first to push it into the drivers/staging which was acked
> > by Greg for the wider testing and review and move into the vanilla tree
> > in the next merge window.
> > 
> > POHMELFS needs two exports from the core VFS: add_to_page_cache_lru and
> > __lock_page_killable.
> > 
> > Please apply given patch to the current tree.
> > 
> > Signed-off-by: Evgeniy Polyakov <zbr@ioremap.net>
> 
> Hm, usually we take exports at the same time the user goes into the
> tree.
> 
> I don't mind adding these exports with the same patch series to add your
> filesystem to the drivers/staging tree, if Andrew and the other vfs
> developers agree it's a sane thing to be exporting.

Ok, I can push them together (just right now :), Andrew, Linus, do you
agree to export those functions?

-- 
	Evgeniy Polyakov

      reply	other threads:[~2009-01-13 21:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 12:43 Add two VFS exports used by POHMELFS Evgeniy Polyakov
2009-01-13 16:56 ` Greg KH
2009-01-13 21:30   ` Evgeniy Polyakov [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=20090113213013.GA27227@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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