From: Martin Wilck <mwilck@suse.com>
To: Hannes Reinecke <hare@suse.de>,
Christophe Varoqui <christophe.varoqui@opensvc.com>,
Benjamin Marzinski <bmarzins@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH 2/4] libmultipath: add_feature: skip pointless NULL check
Date: Tue, 29 Aug 2017 09:21:57 +0200 [thread overview]
Message-ID: <1503991317.4528.0.camel@suse.com> (raw)
In-Reply-To: <59b6a581-78e2-1020-a85e-bb7a151b8986@suse.de>
On Tue, 2017-08-29 at 08:37 +0200, Hannes Reinecke wrote:
> On 08/29/2017 12:05 AM, Martin Wilck wrote:
> > The case f == NULL is already handled by the code from
> > b1ecdd46b6ec "segment faulty occured in add_feature()" above.
> >
> >
> At one point we should have a test case for adding/removing
> features...
I'm actually working on it.
Martin
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2017-08-29 7:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 22:05 [PATCH 1/4] multipathd: don't flood system with sd_notify calls Martin Wilck
2017-08-28 22:05 ` [PATCH 2/4] libmultipath: add_feature: skip pointless NULL check Martin Wilck
2017-08-29 6:37 ` Hannes Reinecke
2017-08-29 7:21 ` Martin Wilck [this message]
2017-09-07 21:33 ` Benjamin Marzinski
2017-08-28 22:05 ` [PATCH 3/4] libmultipath: add_feature: allow only 1 feature Martin Wilck
2017-08-29 6:39 ` Hannes Reinecke
2017-09-07 21:42 ` Benjamin Marzinski
2017-09-07 22:37 ` Benjamin Marzinski
2017-08-28 22:05 ` [PATCH 4/4] multipath: delegate dangerous commands to multipathd Martin Wilck
2017-08-29 6:40 ` Hannes Reinecke
2017-09-07 21:57 ` Benjamin Marzinski
2017-09-08 8:16 ` Martin Wilck
2017-08-29 6:36 ` [PATCH 1/4] multipathd: don't flood system with sd_notify calls Hannes Reinecke
2017-09-07 21:31 ` Benjamin Marzinski
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=1503991317.4528.0.camel@suse.com \
--to=mwilck@suse.com \
--cc=bmarzins@redhat.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox