All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 0/5] Fix checkpointing - invasive
Date: Tue, 20 Feb 2024 14:07:06 +0100	[thread overview]
Message-ID: <20240220140706.000019c1@linux.intel.com> (raw)
In-Reply-To: <20240118103019.12385-1-mateusz.kusiak@intel.com>

On Thu, 18 Jan 2024 11:30:14 +0100
Mateusz Kusiak <mateusz.kusiak@intel.com> wrote:

> This is the second half of splitted patchset "Fix checkpointing" as
> asked. It contains invasive changes regarding checkpoint handling,
> that should not be merged prior to release.
> 
> Note, this patchset applies on the first part "Fix checkpointing -
> minors".
> 
> Mateusz Kusiak (5):
>   Remove hardcoded checkpoint interval checking
>   monitor: refactor checkpoint update
>   Super-intel: Fix first checkpoint restart
>   Grow: Move update_tail assign to Grow_reshape()
>   Add understanding output section in man
> 
>  Grow.c        | 13 ++++++-----
>  mdadm.8.in    | 21 ++++++++++++++++-
>  monitor.c     | 65 +++++++++++++++++++++------------------------------
>  super-intel.c |  3 +++
>  4 files changed, 57 insertions(+), 45 deletions(-)
> 

Applied!

Thanks,
Mariusz

      parent reply	other threads:[~2024-02-20 13:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 10:30 [PATCH v2 0/5] Fix checkpointing - invasive Mateusz Kusiak
2024-01-18 10:30 ` [PATCH v2 1/5] Remove hardcoded checkpoint interval checking Mateusz Kusiak
2024-01-18 10:30 ` [PATCH v2 2/5] monitor: refactor checkpoint update Mateusz Kusiak
2024-01-18 10:30 ` [PATCH v2 3/5] Super-intel: Fix first checkpoint restart Mateusz Kusiak
2024-01-18 10:30 ` [PATCH v2 4/5] Grow: Move update_tail assign to Grow_reshape() Mateusz Kusiak
2024-01-18 10:30 ` [PATCH v2 5/5] Add understanding output section in man Mateusz Kusiak
2024-02-20 13:07 ` 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=20240220140706.000019c1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.