From: Marius Bakke <marius@devup.no>
To: Martin Wilck <mwilck@suse.com>, dm-devel@redhat.com
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>
Subject: Re: [PATCH] multipath-tools: Fix compiler warnings when built without systemd.
Date: Wed, 17 Jun 2020 01:17:57 +0200 [thread overview]
Message-ID: <87d05yeh22.fsf@gnu.org> (raw)
In-Reply-To: <d909fc0a2383f028ae7c3ad00c142193ca8d9ae7.camel@suse.com>
Martin Wilck <mwilck@suse.com> writes:
> Hello Marius,
>
> On Sat, 2020-05-16 at 19:55 +0200, Marius Bakke wrote:
>> ---
>> libmultipath/config.c | 2 +-
>> multipathd/main.c | 19 +++++++++++++------
>> 2 files changed, 14 insertions(+), 7 deletions(-)
>>
>
> thank you for the patch, and sorry for the late reply.
> Thanks to Xose, too, for making me aware of it.
>
> This patch needs some improvements, see remarks below.
>
> In general, please note that the development and in particular the
> testing of multipath-tools has been done almost exclusively on systems
> using systemd for several years now. The compilation issues you
> encountered may only be the tip of the iceberg. In particular, the udev
> rules shipped with multipath-tools rely on systemd for proper device
> setup.
Thanks for reviewing. I'm mainly here for 'kpartx' anyway, but "good"
to know that multipath-tools may need extra care outside of systemd.
I'm hardly a C programmer, so thanks for bearing with me. Adding just
plain old ifdef guards is much clearer than sprinkling __attribute__
around.
V2 sent in a separate message.
Thanks,
Marius
prev parent reply other threads:[~2020-06-16 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 17:55 [PATCH] multipath-tools: Fix compiler warnings when built without systemd Marius Bakke
2020-06-12 2:25 ` Xose Vazquez Perez
2020-06-16 21:53 ` Martin Wilck
2020-06-16 23:11 ` [PATCH v2] multipath: " Marius Bakke
2020-06-17 7:28 ` Martin Wilck
2020-06-16 23:17 ` Marius Bakke [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=87d05yeh22.fsf@gnu.org \
--to=marius@devup.no \
--cc=dm-devel@redhat.com \
--cc=mwilck@suse.com \
--cc=xose.vazquez@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox