From: David Teigland <teigland@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] dlm updates for 2.6.31
Date: Fri, 12 Jun 2009 14:39:18 -0500 [thread overview]
Message-ID: <20090612193917.GA31741@redhat.com> (raw)
Linus,
Please pull dlm updates for 2.6.31 from:
git://git.kernel.org/pub/scm/linux/kernel/git/teigland/dlm.git for-linus
They have all been in linux-next for quite a while, and are all minor
changes/fixes.
Dave
fs/dlm/dir.c | 7 ++++---
fs/dlm/lockspace.c | 17 ++++++++---------
fs/dlm/lowcomms.c | 22 ++++++++++++++++++----
fs/dlm/lowcomms.h | 3 ++-
fs/dlm/member.c | 19 +++++++++++++------
fs/dlm/requestqueue.c | 2 +-
include/linux/dlm.h | 4 ++--
7 files changed, 48 insertions(+), 26 deletions(-)
Christine Caulfield (1):
dlm: connect to nodes earlier
David Teigland (2):
dlm: fix use count with multiple joins
dlm: use more NOFS allocation
Geert Uytterhoeven (1):
dlm: Make name input parameter of {,dlm_}new_lockspace() const
reply other threads:[~2009-06-12 19:48 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=20090612193917.GA31741@redhat.com \
--to=teigland@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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