All of lore.kernel.org
 help / color / mirror / Atom feed
From: mbroz@sourceware.org <mbroz@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/lib/locking locking.h
Date: 3 Dec 2011 11:36:11 -0000	[thread overview]
Message-ID: <20111203113611.28192.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	mbroz at sourceware.org	2011-12-03 11:36:10

Modified files:
	lib/locking    : locking.h 

Log message:
	Fix FIXME and comment :-)

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/locking/locking.h.diff?cvsroot=lvm2&r1=1.71&r2=1.72

--- LVM2/lib/locking/locking.h	2011/12/03 11:34:35	1.71
+++ LVM2/lib/locking/locking.h	2011/12/03 11:36:10	1.72
@@ -94,7 +94,7 @@
 #define LCK_NONBLOCK	0x00000010U	/* Don't block waiting for lock? */
 #define LCK_HOLD	0x00000020U	/* Hold lock when lock_vol returns? */
 #define LCK_LOCAL	0x00000040U	/* Don't propagate to other nodes */
-// FIXME: not used in lock bit byte
+// FIXME: not used in lock bits
 //#define LCK_CLUSTER_VG	0x00000080U	/* VG is clustered */
 #define LCK_CACHE	0x00000100U	/* Operation on cache only using P_ lock */
 #define LCK_ORIGIN_ONLY	0x00000200U	/* Operation should bypass any snapshots */
@@ -111,7 +111,7 @@
 #define LCK_ORIGIN_ONLY_MODE		0x20	/* Same as above */
 #define LCK_DMEVENTD_MONITOR_IGNORE     0x40	/* Whether to ignore dmeventd */
 
-// FIXME: conlict here (CLUSTER_VG is used in lock bits byte)
+// FIXME: conflict here (CLUSTER_VG is used here)
 #define LCK_REVERT_MODE			0x80	/* Remove inactive tables */
 #define LCK_CLUSTER_VG			0x80	/* VG is clustered */
 



             reply	other threads:[~2011-12-03 11:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03 11:36 mbroz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-04-24 12:17 LVM2/lib/locking locking.h zkabelac
2012-02-27  9:52 zkabelac
2011-12-08 18:09 agk
2011-12-03 11:34 mbroz
2010-05-19  1:49 agk
2009-10-01 14:15 ccaulfield
2009-07-24 18:26 agk
2007-11-15  2:55 agk

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=20111203113611.28192.qmail@sourceware.org \
    --to=mbroz@sourceware.org \
    --cc=lvm-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: 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.