From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@linux.intel.com>
To: Jes Sorensen <jsorensen@fb.com>, Jes Sorensen <jes@trained-monkey.org>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>, Coly Li <colyli@suse.de>
Subject: Re: [PATCH] mdadm: split off shared library
Date: Fri, 1 Oct 2021 12:44:40 +0200 [thread overview]
Message-ID: <32212d11-204c-eebb-d84a-7e51d61f53b3@linux.intel.com> (raw)
In-Reply-To: <fc647fe7-542e-d8d0-920f-33a4edf92962@suse.de>
On 26.08.2021 18:28, Coly Li wrote:
> Hi Hannes,
>
> It is fine for me to receiving a series with 30+ patches in linux-raid mailing
> list. And I also can help to review all the patches when they are posted out.
>
> Hi Jes,
>
> If you are too busy to take care of mdadm, and you are glad, it is OK for me to
> take the mdadm maintenance. I can be long term stable for the maintenance task.
Hi Jes,
We have around 40 to 50 patches waiting. We are also waiting for official
4.2 release (it was proposed by me in Jan'21 but it was initially mentioned in
Jul'20!). My preposition for stable release plan was also ignored[1].
I understand that you are busy and mdadm is not in your mind right now.
Coly comes with offer to take care of mdadm, could you answer?
Current model doesn't work, we definitely need to find new solution.
If there any other folk interested in this position, please
speak up loudly!
I will be pleased to cooperate with Coly, or any other maintainer which is
active and responsible. Naturally, VROC team will give support,
especially with external management issues.
It is a time to change something, we shouldn't wait more.
Thanks,
Mariusz
[1]
https://lore.kernel.org/linux-raid/de867ab3-9942-77a0-c14d-dbfc67465888@linux.intel.com/
next prev parent reply other threads:[~2021-10-01 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 14:35 [PATCH] mdadm: split off shared library Hannes Reinecke
2021-08-26 16:28 ` Coly Li
2021-10-01 10:44 ` Tkaczyk, Mariusz [this message]
2021-10-05 9:24 ` Paul Menzel
2021-09-14 7:08 ` Xiao Ni
2021-09-14 7:26 ` Hannes Reinecke
2021-09-14 7:56 ` Xiao Ni
2021-10-06 10:58 ` 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=32212d11-204c-eebb-d84a-7e51d61f53b3@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=colyli@suse.de \
--cc=hare@suse.de \
--cc=jes@trained-monkey.org \
--cc=jsorensen@fb.com \
--cc=linux-raid@vger.kernel.org \
/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).