linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@trained-monkey.org>
To: "Tkaczyk, Mariusz" <mariusz.tkaczyk@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: [PATCH 0/4] mdmonitor improvements
Date: Wed, 14 Oct 2020 11:30:51 -0400	[thread overview]
Message-ID: <07e08c65-b7a7-e42e-4d3d-45e8e296cbf5@trained-monkey.org> (raw)
In-Reply-To: <SA0PR11MB454223C46AAB3F629BEEC22CFF320@SA0PR11MB4542.namprd11.prod.outlook.com>

On 9/29/20 10:34 AM, Tkaczyk, Mariusz wrote:
> Hi Jes,
> Do you receive whole patchset?
> If not let me know. I will send it again.
> I don't know why two patches were lost, I cannot find them anywhere on linux-raid.
> 
> Thanks,
> Mariusz

Hi Mariusz,

I got four patches. Sorry I have been completely swamped with other
stuff at work the last couple of months, so I have gotten behind on this.

I'll try and go through them now.

Thanks,
Jes

> -----Original Message-----
> From: linux-raid-owner@vger.kernel.org <linux-raid-owner@vger.kernel.org> On Behalf Of Mariusz Tkaczyk
> Sent: Wednesday, September 9, 2020 10:31 AM
> To: jes@trained-monkey.org
> Cc: linux-raid@vger.kernel.org
> Subject: [PATCH 0/4] mdmonitor improvements
> 
> This patchset is targeting issues observed across distributions:
> - polling on a wrong resource when mdstat is empty
> - eventing for external containers
> - dealing with udev and mdadm
> - quiet fail if other instance is running
> 
> Mdmonitor is started automitically if needed by udev. This patchset introduces mdmonitor stoping if no redundant array presents.
> 
> Blazej Kucman (2):
>   mdmonitor: set small delay once
>   Check if other Monitor instance running before fork.
> 
> Mariusz Tkaczyk (2):
>   Monitor: refresh mdstat fd after select
>   Monitor: stop notifing about containers.
> 
>  Monitor.c | 83 ++++++++++++++++++++++++++++++++++++++++---------------
>  mdadm.h   |  2 +-
>  mdstat.c  | 20 +++++++++++---
>  3 files changed, 77 insertions(+), 28 deletions(-)
> 
> --
> 2.25.0
> 


  reply	other threads:[~2020-10-14 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09  8:31 [PATCH 0/4] mdmonitor improvements Mariusz Tkaczyk
2020-09-09  8:31 ` [PATCH 3/4] mdmonitor: set small delay once Mariusz Tkaczyk
2020-09-15 11:33   ` Nix
2020-10-14 15:35     ` Jes Sorensen
2020-09-09  8:31 ` [PATCH 4/4] Check if other Monitor instance running before fork Mariusz Tkaczyk
2020-10-14 15:38   ` Jes Sorensen
2020-09-29 14:34 ` [PATCH 0/4] mdmonitor improvements Tkaczyk, Mariusz
2020-10-14 15:30   ` Jes Sorensen [this message]
     [not found] ` <20200909083120.10396-2-mariusz.tkaczyk@intel.com>
2020-10-14 15:34   ` [PATCH 1/4] Monitor: refresh mdstat fd after select Jes Sorensen
     [not found] ` <20200909083120.10396-3-mariusz.tkaczyk@intel.com>
2020-10-14 15:34   ` [PATCH 2/4] Monitor: stop notifing about containers 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=07e08c65-b7a7-e42e-4d3d-45e8e296cbf5@trained-monkey.org \
    --to=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mariusz.tkaczyk@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).