From: Joel Becker <Joel.Becker@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
Sunil Mushran <sunil.mushran@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [GIT PULL] ocfs2 update for 2.6.33
Date: Mon, 4 Jan 2010 17:38:23 -0800 [thread overview]
Message-ID: <20100105013823.GD19331@mail.oracle.com> (raw)
Hey Linus,
Here's the one fix that conflicted against master. I rebased it
atop master and let it stew in linux-next for a little bit. It's an
important fix, getting O_DIRECT correct as we CoW a refcounted cluster.
Please pull.
Joel
The following changes since commit 6b7b284958d47b77d06745b36bc7f36dab769d9b:
Linus Torvalds (1):
Linux 2.6.33-rc2
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2 upstream-linus
Tao Ma (1):
ocfs2: Handle O_DIRECT when writing to a refcounted cluster.
fs/ocfs2/file.c | 21 +++++++++++++++------
1 files changed, 15 insertions(+), 6 deletions(-)
--
"Every day I get up and look through the Forbes list of the richest
people in America. If I'm not there, I go to work."
- Robert Orben
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel at oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-devel
WARNING: multiple messages have this Message-ID (diff)
From: Joel Becker <Joel.Becker@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
Sunil Mushran <sunil.mushran@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [GIT PULL] ocfs2 update for 2.6.33
Date: Mon, 4 Jan 2010 17:38:23 -0800 [thread overview]
Message-ID: <20100105013823.GD19331@mail.oracle.com> (raw)
Hey Linus,
Here's the one fix that conflicted against master. I rebased it
atop master and let it stew in linux-next for a little bit. It's an
important fix, getting O_DIRECT correct as we CoW a refcounted cluster.
Please pull.
Joel
The following changes since commit 6b7b284958d47b77d06745b36bc7f36dab769d9b:
Linus Torvalds (1):
Linux 2.6.33-rc2
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2 upstream-linus
Tao Ma (1):
ocfs2: Handle O_DIRECT when writing to a refcounted cluster.
fs/ocfs2/file.c | 21 +++++++++++++++------
1 files changed, 15 insertions(+), 6 deletions(-)
--
"Every day I get up and look through the Forbes list of the richest
people in America. If I'm not there, I go to work."
- Robert Orben
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
next reply other threads:[~2010-01-05 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 1:38 Joel Becker [this message]
2010-01-05 1:38 ` [GIT PULL] ocfs2 update for 2.6.33 Joel Becker
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=20100105013823.GD19331@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=sunil.mushran@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 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.