Re: [PATCH] mdadm: split off shared library

[Coly Li <colyli@suse.de>]

On 8/25/21 10:35 PM, Hannes Reinecke wrote:
> Hi all,
>
> this is, contrary to the subject, not a patch, but rather a question on
> how to submit a patchset.
> I've been working on splitting off a shared library from mdadm, with the
> aim that it can be included from other programs.
> Reasoning behind it that I've written a monitor program
> (github.com:/hreinecke/md_monitor) and found it a major pain having to
> exec() mdadm, and then keep fingers crossed that things succeed; error
> recovery from _that_ turned out to be a major drag. And so I figured
> that a shared library is possibly the best way to go.
>
> (And, as a side note: having a shared library would also allow to build
> a python binding, which possibly will have even more use-cases ...)
>
> So I've build a patchset to split off a shared library from mdadm, and
> build mdadm against that:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/hare/mdadm.git
> branch shlib
>
> But as it turns out, these are 30+ patches, and I didn't want to flood
> the mailinglist with that.
> So what are the procedures here?
>
> Are you okay with having the entire patchset on the mailing list?
> Or are there other ways?

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.

Thanks.

Coly Li