From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S940575AbcJXOjo (ORCPT ); Mon, 24 Oct 2016 10:39:44 -0400 Received: from b.ns.miles-group.at ([95.130.255.144]:44723 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932878AbcJXOjn (ORCPT ); Mon, 24 Oct 2016 10:39:43 -0400 Subject: Re: [PATCH] MAINTAINERS: add more people to the MTD maintainer team To: Boris Brezillon , Marek Vasut , Cyrille Pitchen , David Woodhouse , Brian Norris , linux-mtd@lists.infradead.org References: <1477312526-7563-1-git-send-email-boris.brezillon@free-electrons.com> Cc: Artem Bityutskiy , linux-kernel@vger.kernel.org, Ezequiel Garcia From: Richard Weinberger Message-ID: Date: Mon, 24 Oct 2016 16:39:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 MIME-Version: 1.0 In-Reply-To: <1477312526-7563-1-git-send-email-boris.brezillon@free-electrons.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Boris, On 24.10.2016 14:35, Boris Brezillon wrote: > Brian has been maintaining the MTD subsystem alone for several years > now, and maintaining such a subsystem can really be time consuming. > > Create a maintainer team formed of the most active MTD contributors > to help Brian with this task, which will hopefully improve the > subsystem reactivity. > > Signed-off-by: Boris Brezillon > --- > Hi all, > > I'm just trying to summarize what I understood the process would be, > don't hesitate to correct me if I'm wrong. > > For each release we will assign a specific MTD maintainer which will be > responsible for taking MTD core patches and pulling spi-nor and nand PRs > into the MTD tree and eventually send one or several PRs to Linus. > > For fixes that are submitted after -rc1, I usually ask Brian to apply > them directly into the MTD tree (I don't think there's a real need to > prepare spi-nor and nand PRs for fixes), so we can proceed the same > way: ask the maintainer assigned to this release to also take care of > applying fixes and sending PRs to Linus before each -rc. > > If you have other ideas, or would like to proceed differently, don't > hesitate propose them. Sounds good to me. Acked-by: Richard Weinberger Thanks, //richard