All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@opensvc.com>
To: Hannes Reinecke <hare@suse.de>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] multipath-tools: use internal drd.h file
Date: Sun, 16 Oct 2016 19:34:46 +0200	[thread overview]
Message-ID: <CABr-GndgxrsHVtJJQg1TBwSU-v1WRo+TKhPVc+S-NjqTt63q2w@mail.gmail.com> (raw)
In-Reply-To: <ea6f0aac-4ca5-e3dd-da71-5a4a1361de64@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 2280 bytes --]

That's why we included a copy of the required valgrind header.
Does this solution eleviate your complain ?

On Sun, Oct 16, 2016 at 6:59 PM, Hannes Reinecke <hare@suse.de> wrote:

> On 10/16/2016 12:26 PM, Xose Vazquez Perez wrote:
>
>> On 10/08/2016 10:22 PM, Xose Vazquez Perez wrote:
>>
>> Cc: Bart Van Assche <bart.vanassche@sandisk.com>
>>> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
>>> Cc: device-mapper development <dm-devel@redhat.com>
>>> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
>>> ---
>>>  libmultipath/debug.c | 2 +-
>>>  multipathd/main.c    | 2 +-
>>>  2 files changed, 2 insertions(+), 2 deletions(-)
>>>
>>
>> This patch is missing.
>> Thank you.
>>
>>
>> diff --git a/libmultipath/debug.c b/libmultipath/debug.c
>>> index 295136c..fbe171a 100644
>>> --- a/libmultipath/debug.c
>>> +++ b/libmultipath/debug.c
>>> @@ -8,7 +8,7 @@
>>>  #include "log_pthread.h"
>>>  #include <sys/types.h>
>>>  #include <time.h>
>>> -#include <../third-party/valgrind/drd.h>
>>> +#include "../third-party/valgrind/drd.h"
>>>  #include "vector.h"
>>>  #include "config.h"
>>>
>>> diff --git a/multipathd/main.c b/multipathd/main.c
>>> index cdfafe8..0998085 100644
>>> --- a/multipathd/main.c
>>> +++ b/multipathd/main.c
>>> @@ -23,7 +23,6 @@
>>>  #endif
>>>  #include <semaphore.h>
>>>  #include <time.h>
>>> -#include <valgrind/drd.h>
>>>
>>>  /*
>>>   * libmultipath
>>> @@ -85,6 +84,7 @@ int uxsock_timeout;
>>>  #include "lock.h"
>>>  #include "waiter.h"
>>>  #include "wwids.h"
>>> +#include "../third-party/valgrind/drd.h"
>>>
>>>  #define FILE_NAME_SIZE 256
>>>  #define CMDSIZE 160
>>>
>>>
>> Please don't.
> We're trying to keep dependencies to each package as small as possible.
> And requiring valgrind by default is not going to help here.
> Please make this a compile-time option.
>
> Cheers,
>
> Hannes
> --
> Dr. Hannes Reinecke                   zSeries & Storage
> hare@suse.de                          +49 911 74053 688
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
> GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

[-- Attachment #1.2: Type: text/html, Size: 3886 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2016-10-16 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-08 20:22 [PATCH] multipath-tools: use internal drd.h file Xose Vazquez Perez
2016-10-10 20:01 ` Bart Van Assche
2016-10-16 10:26 ` Xose Vazquez Perez
2016-10-16 15:54   ` Christophe Varoqui
2016-10-16 16:59   ` Hannes Reinecke
2016-10-16 17:34     ` Christophe Varoqui [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=CABr-GndgxrsHVtJJQg1TBwSU-v1WRo+TKhPVc+S-NjqTt63q2w@mail.gmail.com \
    --to=christophe.varoqui@opensvc.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    /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.