From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: dlm: constify a couple of DLM calls
Date: Fri, 13 Jun 2008 09:44:36 -0500 [thread overview]
Message-ID: <20080613144436.GA7183@redhat.com> (raw)
In-Reply-To: <1213367742.4011.38.camel@quoit>
On Fri, Jun 13, 2008 at 03:35:42PM +0100, Steven Whitehouse wrote:
>
> This patch adds some consts to the DLM in a few places. This means that
> the interfaces to new lockspace and the lock commands can take const
> pointers for the lock space name and lock name respectively. I noticed
> that the lock name is a void * in the header file, but a char *
> internally to DLM. Perhaps the interface and the internal type should be
> changed to match?
Thanks, I'll add this to dlm.git. In theory resource names can be binary
blobs, but in practice we assume they're strings to print them.
prev parent reply other threads:[~2008-06-13 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 14:35 [Cluster-devel] dlm: constify a couple of DLM calls Steven Whitehouse
2008-06-13 14:44 ` David Teigland [this message]
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=20080613144436.GA7183@redhat.com \
--to=teigland@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 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 NNTP newsgroup(s).