From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: Martin Wilck <mwilck@suse.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH 0/2] multipath-tools: avoid error messages with NVMe
Date: Tue, 2 Oct 2018 12:36:58 -0500 [thread overview]
Message-ID: <20181002173658.GU3172@octiron.msp.redhat.com> (raw)
In-Reply-To: <20181001184507.4162-1-mwilck@suse.com>
On Mon, Oct 01, 2018 at 08:45:05PM +0200, Martin Wilck wrote:
> These two patches avoid useless error messages for NVMe devices.
ACK for the set
-Ben
>
> Martin Wilck (2):
> libmultipath: allow sysfs_pathinfo to return SKIPPED
> multipathd: try SCSI persistent reservations for SCSI only
>
> libmultipath/discovery.c | 86 +++++++++++++++++++++-------------------
> multipathd/main.c | 3 ++
> 2 files changed, 48 insertions(+), 41 deletions(-)
>
> --
> 2.19.0
prev parent reply other threads:[~2018-10-02 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 18:45 [PATCH 0/2] multipath-tools: avoid error messages with NVMe Martin Wilck
2018-10-01 18:45 ` [PATCH 1/2] libmultipath: allow sysfs_pathinfo to return SKIPPED Martin Wilck
2018-10-01 18:45 ` [PATCH 2/2] multipathd: try SCSI persistent reservations for SCSI only Martin Wilck
2018-10-01 20:19 ` Christoph Hellwig
2018-10-02 17:36 ` 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=20181002173658.GU3172@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.