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 cleanups and fixes
Date: Fri, 29 Jun 2007 03:26:16 -0400 [thread overview]
Message-ID: <1183101981740-git-send-email-jsipek@cs.sunysb.edu> (raw)
The following patches consist of mostly cleanups and bug fixes of the
Unionfs code.
As before, there is a git repo at:
git://git.kernel.org/pub/scm/linux/kernel/git/jsipek/unionfs.git
(master.kernel.org:/pub/scm/linux/kernel/git/jsipek/unionfs.git)
There are 5 new commits:
Erez Zadok (4):
Unionfs: Convert all instances of "hidden" to "lower"
Unionfs: Use file->f_path instead of file->f_dentry
Unionfs: Clarification comment for unionfs_lookup
Unionfs: Remove unnecessary BUG_ON in unionfs_follow_link
Josef 'Jeff' Sipek (1):
Unionfs: Add missing unlock call in unionfs_file_release
Thanks,
Josef 'Jeff' Sipek <jsipek@cs.sunysb.edu>
next reply other threads:[~2007-06-29 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 7:26 Josef 'Jeff' Sipek [this message]
2007-06-29 7:26 ` [PATCH 1/5] Unionfs: Convert all instances of "hidden" to "lower" Josef 'Jeff' Sipek
2007-06-29 7:26 ` [PATCH 2/5] Unionfs: Add missing unlock call in unionfs_file_release Josef 'Jeff' Sipek
2007-06-29 7:26 ` [PATCH 3/5] Unionfs: Use file->f_path instead of file->f_dentry Josef 'Jeff' Sipek
2007-06-29 7:26 ` [PATCH 4/5] Unionfs: Clarification comment for unionfs_lookup Josef 'Jeff' Sipek
2007-06-29 7:26 ` [PATCH 5/5] Unionfs: Remove unnecessary BUG_ON in unionfs_follow_link Josef 'Jeff' Sipek
-- strict thread matches above, loose matches on Subject: below --
2007-05-24 0:35 [GIT PULL -mm] Unionfs cleanups and fixes 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=1183101981740-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).