public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Cc: ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: [git patches] ocfs2 updates
Date: Mon, 6 Mar 2006 14:36:00 -0800	[thread overview]
Message-ID: <20060306223600.GC27280@ca-server1.us.oracle.com> (raw)

Please pull from 'upstream-linus' branch of
git://oss.oracle.com/home/sourcebo/git/ocfs2.git

to receive the following updates:

 fs/ocfs2/alloc.c             |   88 ++++++++--------
 fs/ocfs2/aops.c              |   18 +--
 fs/ocfs2/buffer_head_io.c    |   11 +-
 fs/ocfs2/cluster/heartbeat.c |   38 +++----
 fs/ocfs2/cluster/masklog.h   |   10 -
 fs/ocfs2/dcache.c            |    9 -
 fs/ocfs2/dir.c               |   42 +++----
 fs/ocfs2/dlm/dlmast.c        |   22 ++--
 fs/ocfs2/dlm/dlmcommon.h     |   21 +++
 fs/ocfs2/dlm/dlmconvert.c    |   11 +-
 fs/ocfs2/dlm/dlmdebug.c      |   18 ++-
 fs/ocfs2/dlm/dlmlock.c       |   14 ++
 fs/ocfs2/dlm/dlmmaster.c     |  227 ++++++++++++++++++++++++++++++++++++-------
 fs/ocfs2/dlm/dlmrecovery.c   |   50 +++++----
 fs/ocfs2/dlm/dlmunlock.c     |   11 +-
 fs/ocfs2/dlmglue.c           |  101 +++++++++----------
 fs/ocfs2/export.c            |   24 ++--
 fs/ocfs2/extent_map.c        |   34 +++---
 fs/ocfs2/file.c              |   42 ++++---
 fs/ocfs2/inode.c             |  116 +++++++++++----------
 fs/ocfs2/journal.c           |   27 ++---
 fs/ocfs2/localalloc.c        |   17 +--
 fs/ocfs2/namei.c             |   79 +++++++-------
 fs/ocfs2/ocfs2.h             |   12 +-
 fs/ocfs2/suballoc.c          |   72 +++++++------
 fs/ocfs2/super.c             |   14 +-
 fs/ocfs2/super.h             |    8 +
 fs/ocfs2/uptodate.c          |   40 ++++---
 fs/ocfs2/vote.c              |   63 ++++++-----
 29 files changed, 749 insertions(+), 490 deletions(-)

Kurt Hackel:
      ocfs2: fix hang in dlm lock resource mastery
      ocfs2: dlm recovery fixes
      ocfs2: don't use MLF* in dlm/ files

Mark Fasheh:
      ocfs2: use __attribute__ format
      ocfs2: don't use MLF* in cluster/ files
      ocfs2: don't use MLF* in the file system
      ocfs2: finally remove MLF* macros

A patch file for the changes can also be found at:

http://oss.oracle.com/~mfasheh/ocfs2-update.patch

It wasn't posted in e-mail because the MLF* updates drove the patch size
past the lkml mail size limit.
	--Mark

--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com

             reply	other threads:[~2006-03-06 22:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 22:36 Mark Fasheh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-12 19:34 [git patches] ocfs2 updates Mark Fasheh
2007-05-25 18:17 Mark Fasheh
2007-04-27 17:23 Mark Fasheh
2006-12-12 18:16 Mark Fasheh
2006-09-21 19:12 Mark Fasheh
2006-08-15 19:20 Mark Fasheh
2006-08-15 19:32 ` Greg KH
2006-06-30  0:05 Mark Fasheh
2006-03-24 23:40 Mark Fasheh
2006-03-01 23:10 Mark Fasheh
2006-03-01 23:37 ` Andrew Morton
2006-03-01 23:52   ` Mark Fasheh
2006-02-16 21:22 Mark Fasheh
2006-02-03 23:02 Mark Fasheh
2006-01-20  1:37 Mark Fasheh

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=20060306223600.GC27280@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=torvalds@osdl.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