From: Alex Zeffertt <alex.zeffertt@eu.citrix.com>
To: "christophe.varoqui@opensvc.com" <christophe.varoqui@opensvc.com>
Cc: "rumcic@gmail.com" <rumcic@gmail.com>, dm-devel <dm-devel@redhat.com>
Subject: Re: [Fwd: [PATCH] Latest git -master is not compilable]
Date: Mon, 8 Feb 2010 10:01:08 +0000 [thread overview]
Message-ID: <4B6FE0E4.7050609@eu.citrix.com> (raw)
In-Reply-To: <1265446918.4273.3.camel@zezette>
The lock() macro is defined in libmultipath/lock.h and just invokes
pthread_mutex_lock() so there'll be no problem replacing the call to lock() with
a call to pthread_mutex_lock().
In the version I was patching (0.4.7) the macros were used everywhere, but in
the latest git master it looks like pthread library calls are invoked directly.
Please change it if it makes the style more consistent.
Regards,
Alex
Christophe Varoqui wrote:
> Can you confirm the fix from Rumko does not break your ulibc setup ?
>
>
>
> ------------------------------------------------------------------------
>
> Subject:
> [PATCH] Latest git -master is not compilable
> From:
> Rumko <rumcic@gmail.com>
> Date:
> Fri, 5 Feb 2010 20:02:23 +0000
> To:
> "christophe.varoqui@opensvc.com" <christophe.varoqui@opensvc.com>
>
> To:
> "christophe.varoqui@opensvc.com" <christophe.varoqui@opensvc.com>
>
>
> Hi!
>
> In latest git -master on line 1443 of multipathd/main.c lock() is called on
> exit_mutex, but since exit_mutex is a pthread_mutex_t, pthread_mutex_lock()
> is needed.
>
> Attached is the one-liner patch, tested it on a gentoo machine and seems to be
> working.
>
prev parent reply other threads:[~2010-02-08 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 9:01 [Fwd: [PATCH] Latest git -master is not compilable] Christophe Varoqui
2010-02-08 10:01 ` Alex Zeffertt [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=4B6FE0E4.7050609@eu.citrix.com \
--to=alex.zeffertt@eu.citrix.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=rumcic@gmail.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.