All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [0/9] pohmelfs for drivers/staging
Date: Thu, 12 Feb 2009 11:41:31 -0800	[thread overview]
Message-ID: <20090212194130.GA16214@kroah.com> (raw)
In-Reply-To: <1234188162-14727-1-git-send-email-zbr@ioremap.net>

On Mon, Feb 09, 2009 at 05:02:33PM +0300, Evgeniy Polyakov wrote:
> Patch is against vanilla tree.

Looks great, I've now added this to the -staging tree and it will show
up in the next -next releases and is queued up to go to Linus for
2.6.30.

thanks,

greg k-h

  parent reply	other threads:[~2009-02-12 20:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 14:02 [0/9] pohmelfs for drivers/staging Evgeniy Polyakov
2009-02-09 14:02 ` [1/9] pohmelfs: documentation Evgeniy Polyakov
2009-02-09 14:02   ` [2/9] pohmelfs: configuration interface Evgeniy Polyakov
2009-02-09 14:02     ` [3/9] pohmelfs: crypto processing Evgeniy Polyakov
2009-02-09 14:02       ` [4/9] pohmelfs: directory operations Evgeniy Polyakov
2009-02-09 14:02         ` [5/9] pohmelfs: inode operations Evgeniy Polyakov
2009-02-09 14:02           ` [6/9] pohmelfs: distributed locking and cache coherency protocol Evgeniy Polyakov
2009-02-09 14:02             ` [7/9] pohmelfs: network operations Evgeniy Polyakov
2009-02-09 14:02               ` [8/9] pohmelfs: transaction layer Evgeniy Polyakov
2009-02-09 14:02                 ` [9/9] pohmelfs: kconfig/makefile and vfs changes Evgeniy Polyakov
2009-02-09 21:30                   ` [10/9] pohmelfs: select crypto modules from the config Evgeniy Polyakov
2009-02-12 19:41 ` Greg KH [this message]
2009-02-12 20:58   ` [0/9] pohmelfs for drivers/staging Evgeniy Polyakov

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=20090212194130.GA16214@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /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.