From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: jes@trained-monkey.org
Cc: linux-raid@vger.kernel.org, colyli@suse.de, xni@redhat.com
Subject: [PATCH 0/4] Few config related refactors
Date: Thu, 23 Mar 2023 17:50:13 +0100 [thread overview]
Message-ID: <20230323165017.27121-1-mariusz.tkaczyk@linux.intel.com> (raw)
Hi Jes,
These patches remove multiple inlines across code and replace them
by defines or functions. No functional changes intended. The goal
is to make this some code reusable for both config and cmdline
(mdadm.c). I next patchset I will start optimizing names verification
(extended v2 of previous patchset).
Mariusz Tkaczyk (4):
mdadm: define DEV_MD_DIR
mdadm: define DEV_NUM_PREF
mdadm: define is_devname_ignore()
mdadm: numbered names verification
Create.c | 7 +++----
Detail.c | 9 ++++-----
Incremental.c | 10 ++++------
Monitor.c | 34 +++++++++++++++++++---------------
config.c | 43 +++++++++++++++++++++----------------------
lib.c | 4 ++--
mapfile.c | 12 ++++++------
mdadm.c | 5 ++---
mdadm.h | 21 ++++++++++++++++++++-
mdopen.c | 16 ++++++++--------
super-ddf.c | 2 +-
super-intel.c | 2 +-
super1.c | 3 +--
sysfs.c | 2 +-
util.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
15 files changed, 137 insertions(+), 77 deletions(-)
--
2.26.2
next reply other threads:[~2023-03-23 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 16:50 Mariusz Tkaczyk [this message]
2023-03-23 16:50 ` [PATCH 1/4] mdadm: define DEV_MD_DIR Mariusz Tkaczyk
2023-03-23 16:50 ` [PATCH 2/4] mdadm: define DEV_NUM_PREF Mariusz Tkaczyk
2023-03-23 16:50 ` [PATCH 3/4] mdadm: define is_devname_ignore() Mariusz Tkaczyk
2023-03-23 16:50 ` [PATCH 4/4] mdadm: numbered names verification Mariusz Tkaczyk
2023-03-24 2:13 ` [PATCH 0/4] Few config related refactors Xiao Ni
2023-04-20 10:46 ` Mariusz Tkaczyk
2023-05-08 20:26 ` Jes Sorensen
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=20230323165017.27121-1-mariusz.tkaczyk@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=colyli@suse.de \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=xni@redhat.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 NNTP newsgroup(s).