All of lore.kernel.org
 help / color / mirror / Atom feed
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 updates/cleanups
Date: Mon, 12 Feb 2007 13:30:49 -0500	[thread overview]
Message-ID: <11713050521708-git-send-email-jsipek@cs.sunysb.edu> (raw)

The following patches (also available though the git tree) fix few
cleanliness issues with Unionfs.

You can pull from 'master' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jsipek/unionfs.git

to receive the following:

Erez Zadok (1):
      Unionfs: Documentation update

Josef 'Jeff' Sipek (2):
      fs/unionfs/: Use __roundup_pow_of_two instead of custom rounding code
      fs/: Move eCryptfs & Unionfs config options into a sub-menu

 Documentation/filesystems/unionfs/00-INDEX   |    8 ++-
 Documentation/filesystems/unionfs/issues.txt |   23 +++++++++
 Documentation/filesystems/unionfs/usage.txt  |   31 ++++--------
 fs/Kconfig                                   |   66 ++++++++++++++------------
 fs/unionfs/main.c                            |    2 +-
 fs/unionfs/rdstate.c                         |   11 +----
 fs/unionfs/union.h                           |    1 +
 7 files changed, 77 insertions(+), 65 deletions(-)

Josef 'Jeff' Sipek.



             reply	other threads:[~2007-02-12 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 18:30 Josef 'Jeff' Sipek [this message]
2007-02-12 18:30 ` [PATCH 1/3] fs/unionfs/: Use __roundup_pow_of_two instead of custom rounding code Josef 'Jeff' Sipek
2007-02-12 18:30 ` [PATCH 2/3] fs/: Move eCryptfs & Unionfs config options into a sub-menu Josef 'Jeff' Sipek
2007-02-12 18:30 ` [PATCH 3/3] Unionfs: Documentation update Josef 'Jeff' Sipek
  -- strict thread matches above, loose matches on Subject: below --
2007-01-29 20:37 [GIT PULL -mm] Unionfs updates/cleanups 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=11713050521708-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.