From: "Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: akpm@linux-foundation.org
Subject: [GIT PULL -mm] Unionfs/eCryptfs cleanups
Date: Sat, 17 Feb 2007 03:56:54 -0500 [thread overview]
Message-ID: <11717026161843-git-send-email-jsipek@cs.sunysb.edu> (raw)
You can pull from 'master' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jsipek/unionfs.git
to receive the following:
Josef 'Jeff' Sipek (1):
fs/unionfs/: Remove unused structure members & macros
Michael Halcrow (1):
eCryptfs: convert lookup_one_len() to lookup_one_len_nd()
fs/ecryptfs/inode.c | 10 ++++++++--
fs/unionfs/union.h | 9 ---------
2 files changed, 8 insertions(+), 11 deletions(-)
Josef 'Jeff' Sipek.
next reply other threads:[~2007-02-17 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 8:56 Josef 'Jeff' Sipek [this message]
2007-02-17 8:56 ` [PATCH 1/2] eCryptfs: convert lookup_one_len() to lookup_one_len_nd() Josef 'Jeff' Sipek
2007-03-09 9:40 ` Christoph Hellwig
2007-03-09 16:34 ` Josef Sipek
2007-02-17 8:56 ` [PATCH 2/2] fs/unionfs/: Remove unused structure members & macros Josef 'Jeff' Sipek
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=11717026161843-git-send-email-jsipek@cs.sunysb.edu \
--to=jsipek@cs.sunysb.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).