From: Martin Wilck <mwilck@suse.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>,
Chongyun Wu <wu.chongyun@h3c.com>
Cc: Martin Wilck <mwilck@suse.com>, dm-devel@redhat.com
Subject: [PATCH RESEND 0/4] multipath-tools: fixes for path wwid detection and path change uevents
Date: Thu, 8 Mar 2018 00:21:48 +0100 [thread overview]
Message-ID: <20180307232152.15538-1-mwilck@suse.com> (raw)
Hi Christophe,
this small series fixes some minor glitches I found in the current path
discovery code, and attempts to implement the safe part of the functionality
discussed in the thread "multipathd: update path's udev in uev_update_path"
in January (based on an idea from Wu Chongyun).
Resending the series, unchanged, rebased on 0.7.5.
Regards,
Martin
Martin Wilck (4):
libmultipath: get_uid: check VPD pages for SCSI only
libmultipath: get_uid: don't quit prematurely without udev
libmultipath: uev_update_path: always warn if WWID changed
libmultipath: uev_update_path: update path properties
libmultipath/discovery.c | 58 ++++++++++++++++++++++++++++--------------------
multipathd/main.c | 29 +++++++++++++++++-------
2 files changed, 55 insertions(+), 32 deletions(-)
--
2.16.1
next reply other threads:[~2018-03-07 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 23:21 Martin Wilck [this message]
2018-03-07 23:21 ` [PATCH RESEND 1/4] libmultipath: get_uid: check VPD pages for SCSI only Martin Wilck
2018-03-07 23:21 ` [PATCH RESEND 2/4] libmultipath: get_uid: don't quit prematurely without udev Martin Wilck
2018-03-07 23:21 ` [PATCH RESEND 3/4] libmultipath: uev_update_path: always warn if WWID changed Martin Wilck
2018-03-07 23:21 ` [PATCH RESEND 4/4] libmultipath: uev_update_path: update path properties Martin Wilck
2018-03-14 17:40 ` [PATCH RESEND 0/4] multipath-tools: fixes for path wwid detection and path change uevents Benjamin Marzinski
2018-10-02 21:02 ` Martin Wilck
2018-10-05 23:07 ` Benjamin Marzinski
2018-10-08 8:26 ` Martin Wilck
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=20180307232152.15538-1-mwilck@suse.com \
--to=mwilck@suse.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=wu.chongyun@h3c.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