From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Brassow Subject: [PATCH 1 of 2 - v2] DM log userspace: Minor fix-ups Date: Wed, 19 Oct 2011 16:02:13 -0500 Message-ID: <1319058133.4668.1.camel@f14.redhat.com> References: <1318533312.28595.4.camel@f14.redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1318533312.28595.4.camel@f14.redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: dm-devel@redhat.com List-Id: dm-devel.ids dm-log-userspace: comment fixes Signed-off-by: Jonathan Brassow Index: linux-upstream/drivers/md/dm-log-userspace-base.c =================================================================== --- linux-upstream.orig/drivers/md/dm-log-userspace-base.c +++ linux-upstream/drivers/md/dm-log-userspace-base.c @@ -146,7 +146,7 @@ static int build_constructor_string(stru * * Where 'other args' is the userspace implementation specific log * arguments. An example might be: - * clustered_disk [[no]sync] + * clustered-disk [[no]sync] * * So, this module will strip off the for identification purposes * when communicating with userspace about a log; but will pass on everything Index: linux-upstream/Documentation/device-mapper/dm-log.txt =================================================================== --- linux-upstream.orig/Documentation/device-mapper/dm-log.txt +++ linux-upstream/Documentation/device-mapper/dm-log.txt @@ -48,7 +48,7 @@ kernel and userspace, 'connector' is use communication. There are currently two userspace log implementations that leverage this -framework - "clustered_disk" and "clustered_core". These implementations +framework - "clustered-disk" and "clustered-core". These implementations provide a cluster-coherent log for shared-storage. Device-mapper mirroring can be used in a shared-storage environment when the cluster log implementations are employed.