From: Joel Becker <Joel.Becker@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [GIT PULL] ocfs2 fixes for 2.6.33
Date: Wed, 23 Dec 2009 13:16:46 -0800 [thread overview]
Message-ID: <20091223211645.GA5502@mail.oracle.com> (raw)
Hey Linus,
This is the first of a couple small ocfs2 pulls for this cycle.
Sorry they are after the merge window; fixes kept dribbling in, and
eventually picked up a conflict against already merged stuff.
This first batch is before that conflict and consists entirely
of fixes. I'm sending them as tested rather than rebasing them. The
next batch will be both fixes and small functional changes.
Please pull.
The following changes since commit 56f3f55cf9b604b924353ab6fcdac5fee5637ae3:
Linus Torvalds (1):
Merge branch 'for-linus' of git://git.kernel.org/.../sameo/mfd-2.6
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2.git upstream-linus
Tao Ma (4):
ocfs2: Find proper end cpos for a leaf refcount block.
ocfs2: refcounttree.c cleanup.
ocfs2: Add reflinked file's inode to inode hash eariler.
ocfs2: Set i_nlink properly during reflink.
fs/ocfs2/alloc.c | 10 ++--
fs/ocfs2/alloc.h | 5 ++
fs/ocfs2/namei.c | 5 +-
fs/ocfs2/refcounttree.c | 150 ++++++++++++++++++++++++++++++++++++----------
4 files changed, 131 insertions(+), 39 deletions(-)
--
"But then she looks me in the eye
And says, 'We're going to last forever,'
And man you know I can't begin to doubt it.
Cause it just feels so good and so free and so right,
I know we ain't never going to change our minds about it, Hey!
Here comes my girl."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-devel
reply other threads:[~2009-12-23 21:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091223211645.GA5502@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=torvalds@linux-foundation.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