linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erez Zadok <ezk@cs.sunysb.edu>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	viro@ftp.linux.org.uk, hch@infradead.org
Subject: [GIT PULL -mm] 0/2 Unionfs updates/fixes/cleanups
Date: Sat,  8 Dec 2007 15:46:03 -0500	[thread overview]
Message-ID: <1197146765464-git-send-email-ezk@cs.sunysb.edu> (raw)


The following is a series of patches related to Unionfs: just a couple of
small bug fixes and/or optimizations.

These patches were tested (where appropriate) on Linus's 2.6.24 latest code
(as of v2.6.24-rc4-124-gf194d13), MM, as well as the backports to
2.6.{23,22,21,20,19,18,9} on ext2/3/4, xfs, reiserfs, nfs2/3/4, jffs2,
ramfs, tmpfs, cramfs, and squashfs (where available).  See
http://unionfs.filesystems.org/ to download back-ported unionfs code.

Please pull from the 'master' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/ezk/unionfs.git

to receive the following:

Erez Zadok (2):
      Unionfs: cleanup/consolidate branch-mode parsing code
      Unionfs: reduce the amount of cache-coherency debugging messages

 dentry.c |   38 +++++++++++++++++++++++---------------
 main.c   |   44 ++++++++++++++++++++++----------------------
 super.c  |   12 ++++++++----
 union.h  |    3 +--
 4 files changed, 54 insertions(+), 43 deletions(-)

---
Erez Zadok
ezk@cs.sunysb.edu

             reply	other threads:[~2007-12-08 20:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08 20:46 Erez Zadok [this message]
2007-12-08 20:46 ` [PATCH 1/2] Unionfs: cleanup/consolidate branch-mode parsing code Erez Zadok
2007-12-08 20:46 ` [PATCH 2/2] Unionfs: reduce the amount of cache-coherency debugging messages Erez Zadok
  -- strict thread matches above, loose matches on Subject: below --
2007-12-14 15:47 [GIT PULL -mm] 0/2 Unionfs updates/fixes/cleanups Erez Zadok
2008-05-09 20:07 Erez Zadok

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=1197146765464-git-send-email-ezk@cs.sunysb.edu \
    --to=ezk@cs.sunysb.edu \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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).