public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: cfeist@sourceware.org To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com Subject: Cluster Project branch, RHEL46, updated. cman-kernel_2_6_9_54-10-g77ccf10 Date: Wed, 16 Apr 2008 20:30:00 -0000 [thread overview] Message-ID: <20080416203003.16047.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Cluster Project". http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=77ccf101d7d00c3048f7c8c2c489d26b9aebddae The branch, RHEL46 has been updated via 77ccf101d7d00c3048f7c8c2c489d26b9aebddae (commit) from 98e82d8e38259f37db87044d1a2446391583d0cf (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 77ccf101d7d00c3048f7c8c2c489d26b9aebddae Author: Chris Feist <cfeist@redhat.com> Date: Wed Apr 16 15:28:33 2008 -0500 Added busy member to posix_lock struct Needed to get bz#440665 to compile. ----------------------------------------------------------------------- Summary of changes: gfs-kernel/src/dlm/lock_dlm.h | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/gfs-kernel/src/dlm/lock_dlm.h b/gfs-kernel/src/dlm/lock_dlm.h index 8807fe7..15f7386 100644 --- a/gfs-kernel/src/dlm/lock_dlm.h +++ b/gfs-kernel/src/dlm/lock_dlm.h @@ -152,6 +152,7 @@ struct posix_lock { uint64_t end; int count; int ex; + int busy; }; #define LFL_NOBLOCK 0 hooks/post-receive -- Cluster Project
reply other threads:[~2008-04-16 20:30 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=20080416203003.16047.qmail@sourceware.org \ --to=cfeist@sourceware.org \ --cc=cluster-cvs@sources.redhat.com \ --cc=cluster-devel@redhat.com \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).