From: Benjamin Marzinski <bmarzins@redhat.com>
To: mwilck@suse.com
Cc: dm-devel@redhat.com
Subject: Re: [PATCH 00/39] multipath-tools series part II: dev_loss_tmo fixes
Date: Thu, 16 Jul 2020 20:05:52 -0500 [thread overview]
Message-ID: <20200717010552.GO11089@octiron.msp.redhat.com> (raw)
In-Reply-To: <20200709101952.7285-1-mwilck@suse.com>
On Thu, Jul 09, 2020 at 12:19:48PM +0200, mwilck@suse.com wrote:
> From: Martin Wilck <mwilck@suse.com>
>
> Hi Christophe, hi Ben,
>
> This is part II of a larger patch series for multpath-tools I've been preparing.
> It contains some minor fixes for dev_loss_tmo handling, mostly logging.
> It's based on the previously submitted part I.
>
> The full series will also be available here:
> https://github.com/mwilck/multipath-tools/tree/ups/submit-2007
>
> There are tags in that repo for each part of the series.
> This part is tagged "submit-200709-2".
>
> Regards,
> Martin
>
Reviewed-by: Benjamin Marzinski <bmarzins@redhat.com>
for the part.
>
> Martin Wilck (4):
> libmultipath: add macro DEV_LOSS_TMO_UNSET
> libmultipath: improve logging for dev_loss_tmo override
> libmultipath: print message if setting dev_loss_tmo is unsupported
> libmultipath: increase log level of limiting dev_loss_tmo
>
> libmultipath/defaults.h | 1 +
> libmultipath/dict.c | 4 +--
> libmultipath/discovery.c | 56 ++++++++++++++++++++++++++++++----------
> libmultipath/propsel.c | 2 +-
> 4 files changed, 46 insertions(+), 17 deletions(-)
>
> --
> 2.26.2
prev parent reply other threads:[~2020-07-17 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 10:19 [PATCH 00/39] multipath-tools series part II: dev_loss_tmo fixes mwilck
2020-07-09 10:19 ` [PATCH 36/39] libmultipath: add macro DEV_LOSS_TMO_UNSET mwilck
2020-07-09 10:19 ` [PATCH 37/39] libmultipath: improve logging for dev_loss_tmo override mwilck
2020-07-09 10:19 ` [PATCH 38/39] libmultipath: print message if setting dev_loss_tmo is unsupported mwilck
2020-07-09 10:19 ` [PATCH 39/39] libmultipath: increase log level of limiting dev_loss_tmo mwilck
2020-07-17 1:05 ` Benjamin Marzinski [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=20200717010552.GO11089@octiron.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mwilck@suse.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.