From: Martin Wilck <martin.wilck@suse.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>,
Benjamin Marzinski <bmarzins@redhat.com>
Cc: dm-devel@lists.linux.dev, Martin Wilck <mwilck@suse.com>
Subject: [PATCH 0/3] libmultipath: use bitwise flags in devmapper API
Date: Thu, 2 May 2024 20:59:43 +0200 [thread overview]
Message-ID: <20240502185946.31192-1-mwilck@suse.com> (raw)
This series goes on top of Benjamin Marzinksi's late "multipath: fix hang
in flush_map_nopaths" series. It introduces no functional changes. It
just combines the multiple boolean arguments to _dm_flush_map() and
dm_simplecmd() into a flags variable. This reduces the number of
function arguments, but that's not the main intention. The symbolic
flags improve the readability of the code by making it obvious which
flags are passed to the respective functions in their callers.
Martin Wilck (3):
libmultipath: use bitwise flags for map flushing API
libmultipath: use bitwise flags for dm_simplecmd API
libmultipath: add argument names to some prototypes
libmultipath/devmapper.c | 94 ++++++++++++++++++----------------------
libmultipath/devmapper.h | 33 +++++++++-----
2 files changed, 62 insertions(+), 65 deletions(-)
--
2.44.0
next reply other threads:[~2024-05-02 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 18:59 Martin Wilck [this message]
2024-05-02 18:59 ` [PATCH 1/3] libmultipath: use bitwise flags for map flushing API Martin Wilck
2024-05-02 18:59 ` [PATCH 2/3] libmultipath: use bitwise flags for dm_simplecmd API Martin Wilck
2024-05-02 18:59 ` [PATCH 3/3] libmultipath: add argument names to some prototypes Martin Wilck
2024-05-03 16:08 ` [PATCH 0/3] libmultipath: use bitwise flags in devmapper API 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=20240502185946.31192-1-mwilck@suse.com \
--to=martin.wilck@suse.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).