From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Mateusz Kusiak <mateusz.kusiak@intel.com>
Cc: linux-raid@vger.kernel.org, jes@trained-monkey.org
Subject: Re: [PATCH 0/8] Fix checkpointing
Date: Wed, 17 Jan 2024 09:02:19 +0100 [thread overview]
Message-ID: <20240117090219.00004174@linux.intel.com> (raw)
In-Reply-To: <20240116112434.30705-1-mateusz.kusiak@intel.com>
On Tue, 16 Jan 2024 12:24:26 +0100
Mateusz Kusiak <mateusz.kusiak@intel.com> wrote:
> Currently there are multiple issues regarding checkpointing in mdadm.
> This patchset fixes most of them.
>
> Thanks,
> Mateusz
>
Hi Mateusz,
I would like to make a release soon, so I won't take them all for now because
risk is high.
For everyone interested in mdadm release, there are few medium risk regressions
in IMSM caused by:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=4dde420fc3e24077ab926f79674eaae1b71de10b
I will start considering a release after resolving them. I expected a patches
on ML within 2 weeks.
From this serie, I can take following patches earlier:
> Define sysfs max buffer size
I think it is safe. I see this conflicting with another patchset I know you are
working on.
> Replace "none" with macro
> super-intel: Remove inaccessible code
These two are rather safe too.
and eventually (if there is no dependency in other patches):
> Add understanding output section in man
Please consider dividing it into 2 series, or sending "Define sysfs max buffer
size" separately.
Thanks,
Mariusz
> Mateusz Kusiak (8):
> Remove hardcoded checkpoint interval checking
> monitor: refactor checkpoint update
> Super-intel: Fix first checkpoint restart
> Define sysfs max buffer size
> Replace "none" with macro
> super-intel: Remove inaccessible code
> Grow: Move update_tail assign to Grow_reshape()
> Add understanding output section in man
>
> Assemble.c | 3 +-
> Build.c | 4 +--
> Create.c | 2 +-
> Grow.c | 64 +++++++++++++++++++-------------------
> Incremental.c | 4 +--
> Manage.c | 10 +++---
> Monitor.c | 6 ++--
> config.c | 2 +-
> managemon.c | 6 ++--
> maps.c | 4 +--
> mdadm.8.in | 21 ++++++++++++-
> mdadm.c | 7 ++---
> mdadm.h | 18 +++++++++++
> monitor.c | 85 ++++++++++++++++++++++-----------------------------
> msg.c | 4 +--
> super-intel.c | 38 ++++++++---------------
> sysfs.c | 12 ++++----
> util.c | 2 +-
> 18 files changed, 151 insertions(+), 141 deletions(-)
>
prev parent reply other threads:[~2024-01-17 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 11:24 [PATCH 0/8] Fix checkpointing Mateusz Kusiak
2024-01-16 11:24 ` [PATCH 1/8] Remove hardcoded checkpoint interval checking Mateusz Kusiak
2024-01-16 11:24 ` [PATCH 2/8] monitor: refactor checkpoint update Mateusz Kusiak
2024-01-16 11:24 ` [PATCH 3/8] Super-intel: Fix first checkpoint restart Mateusz Kusiak
2024-01-16 11:24 ` [PATCH 4/8] Define sysfs max buffer size Mateusz Kusiak
2024-01-16 11:24 ` [PATCH 5/8] Replace "none" with macro Mateusz Kusiak
2024-01-16 11:24 ` [PATCH 6/8] super-intel: Remove inaccessible code Mateusz Kusiak
2024-01-16 11:24 ` [PATCH 7/8] Grow: Move update_tail assign to Grow_reshape() Mateusz Kusiak
2024-01-16 11:24 ` [PATCH 8/8] Add understanding output section in man Mateusz Kusiak
2024-01-17 8:02 ` Mariusz Tkaczyk [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=20240117090219.00004174@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=mateusz.kusiak@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 NNTP newsgroup(s).