linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Shaohua Li <shli@kernel.org>
Cc: linux-raid@vger.kernel.org, dm-devel@redhat.com,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Phil Turmel <philip@turmel.org>
Subject: Re: WANTED new maintainer for Linux/md (and mdadm)
Date: Fri, 08 Jan 2016 13:38:24 +1100	[thread overview]
Message-ID: <8760z4aj8f.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20160104182402.GA1541@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]

On Tue, Jan 05 2016, Shaohua Li wrote:

>
> Hi Neil,
>
> Thanks for all the efforts! We will definitely miss you and fortunately you
> won't completely quit from MD :). I'm very interested in helping maintain MD. I
> have been working on MD for several years. My employer (facebook) supports me,
> so I have time being a maintainer too.

Hi Shaohua,
 as you are one of the more active developers of MD at the moment, this
 probably affects you more than many others and your willingness to
 contribute more is certainly welcome.

 The first question is where do you send your patches to get the
 appropriate review and upstream acceptance.  Alasdair or Mike (DM),
 Jens (Block), Andrew Morton (anything) and Linus (everything) are all
 defensible choices for upstreaming (I've submitted through Andrew in
 the past, but through Linus exclusively once I figured out git).  That
 is really something you and they would need to negotiate though.

 I plan to submit a pull request to Linus for the 4.5 merge window
 and then stop queuing patches.  I will still review your journaling
 patches but will likely reply with "Reviewed-by" rather than "applied,
 thanks".
 My intention is to only look at other patches if they already have an
 independent "Reviewed-by", but it remains to be seen how strongly I
 stick to that intention.

 If you have specific questions about anything (md internals, git
 work-flows, whatever) do feel free to ask.
 I am trying to write some comprehensive documentation on the internals
 of MD - though it is slow going.  Once that is mostly done I'll make it
 available and it should at least serve as a good structure in which to
 place answers to further questions.

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2016-01-08  2:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21  6:10 WANTED new maintainer for Linux/md (and mdadm) NeilBrown
2015-12-21 12:28 ` Phil Turmel
2016-01-04 10:16 ` [dm-devel] " Sebastian Parschauer
2016-01-04 18:24 ` Shaohua Li
2016-01-08  2:38   ` NeilBrown [this message]
2016-01-04 20:40 ` [dm-devel] " Brassow Jonathan
2016-01-06 16:53   ` Jes Sorensen
2016-01-08  2:17     ` NeilBrown
2016-01-08 20:28       ` Jes Sorensen
2016-01-20  8:27 ` Artur Paszkiewicz
2016-01-26 23:01   ` NeilBrown
2016-02-02 12:19     ` 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=8760z4aj8f.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=bfields@fieldses.org \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.org \
    --cc=shli@kernel.org \
    --cc=torvalds@linux-foundation.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).