From: Mateusz Kusiak <mateusz.kusiak@intel.com>
To: linux-raid@vger.kernel.org
Cc: jes@trained-monkey.org, mariusz.tkaczyk@linux.intel.com
Subject: [PATCH v2 0/3] Fix checkpointing - minors
Date: Thu, 18 Jan 2024 11:28:39 +0100 [thread overview]
Message-ID: <20240118102842.12304-1-mateusz.kusiak@intel.com> (raw)
This is the first half of splitted patchset "Fix checkpointing" as
asked. It contains minor changes that should be safe to merge prior to
release.
Fixed minor things in "Replace "none" with macro":
- Replaced hardcoded "null" size to "sizeof(STR_COMMON_NONE) - 1"
in str_is_none().
- Removed is_none() on optarg as it checked only first four chars,
bad for user input.
I included "Add understanding output section in man" in second patchset
to preserve history (adding it here, prior to release might seem
random).
Mateusz Kusiak (3):
Define sysfs max buffer size
Replace "none" with macro
super-intel: Remove inaccessible code
Assemble.c | 3 +--
Build.c | 4 ++--
Create.c | 2 +-
Grow.c | 51 +++++++++++++++++++++++++--------------------------
Incremental.c | 4 ++--
Manage.c | 10 +++++-----
Monitor.c | 6 +++---
config.c | 2 +-
managemon.c | 6 +++---
maps.c | 4 ++--
mdadm.c | 7 +++----
mdadm.h | 18 ++++++++++++++++++
monitor.c | 24 ++++++++++++------------
msg.c | 4 ++--
super-intel.c | 35 +++++++++--------------------------
sysfs.c | 12 ++++++------
util.c | 2 +-
17 files changed, 96 insertions(+), 98 deletions(-)
--
2.35.3
next reply other threads:[~2024-01-18 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 10:28 Mateusz Kusiak [this message]
2024-01-18 10:28 ` [PATCH v2 1/3] Define sysfs max buffer size Mateusz Kusiak
2024-01-18 10:28 ` [PATCH v2 2/3] Replace "none" with macro Mateusz Kusiak
2024-01-18 10:28 ` [PATCH v2 3/3] super-intel: Remove inaccessible code Mateusz Kusiak
2024-01-24 15:19 ` [PATCH v2 0/3] Fix checkpointing - minors Mariusz Tkaczyk
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=20240118102842.12304-1-mateusz.kusiak@intel.com \
--to=mateusz.kusiak@intel.com \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.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).