public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
Cc: hooanon05@yahoo.co.jp, linux-fsdevel@vger.kernel.org,
	ecryptfs-devel@lists.launchpad.net, linux-kernel@vger.kernel.org,
	mhalcrow@us.ibm.com
Subject: Re: [Ecryptfs-devel] [PATCH] ecryptfs: some inode attrs, and a question
Date: Thu, 15 Jan 2009 15:51:43 -0800	[thread overview]
Message-ID: <20090115155143.e4509e7e.akpm@linux-foundation.org> (raw)
In-Reply-To: <496FC91C.10806@linux.vnet.ibm.com>

On Thu, 15 Jan 2009 17:39:08 -0600
Tyler Hicks <tyhicks@linux.vnet.ibm.com> wrote:

> > I am puzzled by the current ecryptfs maintenance situation.
> > 
> 
> http://article.gmane.org/gmane.linux.kernel/768122
> 
> The torch has been passed to me.  :)

yup, thanks.

> > I queued this for 2.6.30.  It could be bumped up for 2.6.29 (and even
> > backported to 2.6.28 and earlier) with suitable acks from the
> > maintainer(?)
> > 
> 
> The changes to ecryptfs_rmdir() are valid, but not the rest of the patch.
> 

OK, I'll drop my copy.  Please send something back at me sometime, with
indications about which kernel version(s) it should be merged into.

We should chase J.R.  for a Signed-off-by:, which was omitted from the
original patch.


  reply	other threads:[~2009-01-15 23:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  6:20 [PATCH] ecryptfs: some inode attrs, and a question hooanon05
2009-01-13 13:17 ` Dave Kleikamp
2009-01-15 21:51   ` [Ecryptfs-devel] " Tyler Hicks
2009-01-16  7:36     ` hooanon05
2009-01-16 16:59       ` Dave Kleikamp
2009-01-17  6:03         ` hooanon05
2009-01-17 16:42           ` Dave Kleikamp
2009-01-17 17:42             ` hooanon05
2009-01-17 18:11               ` Dave Kleikamp
2009-01-19  2:17                 ` hooanon05
2009-01-19 15:01                   ` Dave Kleikamp
2009-01-19 15:25                     ` hooanon05
2009-01-19 15:30                       ` Dave Kleikamp
2009-01-19 15:35                         ` hooanon05
2009-01-19  2:15               ` hooanon05
2009-01-16  8:04     ` hooanon05
2009-01-15 23:03 ` Andrew Morton
2009-01-15 23:39   ` [Ecryptfs-devel] " Tyler Hicks
2009-01-15 23:51     ` Andrew Morton [this message]
2009-01-16  7:42   ` hooanon05
2009-01-16  7:53     ` Andrew Morton

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=20090115155143.e4509e7e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ecryptfs-devel@lists.launchpad.net \
    --cc=hooanon05@yahoo.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhalcrow@us.ibm.com \
    --cc=tyhicks@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox