From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Halcrow <mhalcrow@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
ecryptfs-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/2] eCryptfs: Introduce device handle for userspace daemon communications
Date: Tue, 15 Apr 2008 14:08:04 -0700 [thread overview]
Message-ID: <20080415140804.4dcd461b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080415202438.GJ18629@localhost.austin.ibm.com>
On Tue, 15 Apr 2008 15:24:38 -0500
Michael Halcrow <mhalcrow@us.ibm.com> wrote:
> Subject: [PATCH 2/2] eCryptfs: Introduce device handle for userspace daemon communications
This patch has the same title as [1/2]. I renamed it to "eCryptfs:
integrate eCryptfs device handle into the module."
next prev parent reply other threads:[~2008-04-15 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 20:23 [PATCH 1/2] eCryptfs: Introduce device handle for userspace daemon communications Michael Halcrow
2008-04-15 20:24 ` [PATCH 2/2] " Michael Halcrow
2008-04-15 21:08 ` Andrew Morton [this message]
2008-04-15 21:04 ` [PATCH 1/2] " Andrew Morton
2008-04-15 21:34 ` Serge E. Hallyn
2008-04-16 19:24 ` [PATCH] eCryptfs: Make key module subsystem respect namespaces Michael Halcrow
2008-04-16 21:10 ` [PATCH] eCryptfs: Remove obsolete netlink interface to daemon Michael Halcrow
2008-04-17 15:34 ` [PATCH] eCryptfs: Make key module subsystem respect namespaces Serge E. Hallyn
2008-04-17 17:03 ` [PATCH] eCryptfs: Fix refs to pid and user_ns Michael Halcrow
2008-04-17 17:41 ` Serge E. Hallyn
2008-04-15 22:47 ` [Ecryptfs-devel] [PATCH 1/2] eCryptfs: Introduce device handle for userspace daemon communications Michael Halcrow
2008-04-15 23:30 ` Michael Halcrow
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=20080415140804.4dcd461b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ecryptfs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.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