Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935590AbcJRTCl (ORCPT ); Tue, 18 Oct 2016 15:02:41 -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 S932230AbcJRTCd (ORCPT ); Tue, 18 Oct 2016 15:02:33 -0400 Subject: Re: [PATCH 1/1] MAINTAINERS: add a maintainer for the SPI NOR subsystem To: Brian Norris References: <0a3eaa21fb0f38743308c9cc9fc5d2373f4877de.1476802288.git.cyrille.pitchen@atmel.com> <3d45f698-08e9-e672-d405-1ab9bfec1222@atmel.com> <20161018184651.GA71760@google.com> Cc: Cyrille Pitchen , Marek Vasut , "linux-mtd@lists.infradead.org" , nicolas.ferre@atmel.com, Boris Brezillon , LKML , David Woodhouse , Artem Bityutskiy , David Oberhollenzer From: Richard Weinberger Message-ID: <09ac9f8a-d6a0-97a8-c73a-ffb53bc1a4c8@nod.at> Date: Tue, 18 Oct 2016 21:02:27 +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: <20161018184651.GA71760@google.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2238 Lines: 54 Brian, On 18.10.2016 20:46, Brian Norris wrote: >>> I totally agree with you so if Marek and you volunteer as well, your help >>> will be precious! >> >> Well, my SPI-NOR fu is not strong. And UBI/UBIFS keeps me busy. >> But if Brian likes the idea of having a MTD maintainer team I'll offer my help. > > I think a MTD maintainer team would be good to try, and I think it might > help to resolve my above complaint; a maintainer team could help to make > sure that everything can be coordinated in one tree + pull request, > without adding too many extra points of failure (e.g., so we don't have > awesome SPI NOR and NAND trees get bogged down by a slow MTD pull). > > Random thoughts: > > Does it make sense to still use infradead.org? We'd need to add a few > users there. What else do you have in mind? kernel.org? As long all users with commit access are member of the kernel.org web of trust any host should be fine. > Trust? I have met most of you in person, but not all, and I don't have > signed keys from all of you. I don't know what the best way to get a > group-writeable repo with credentials for all of you that we can trust. > (FWIW, neither Artem nor David met me, but they saw it fit to grant me > infradead.org access ;) ) I'd go with the kernel.org web of trust. > Coordination: how do we avoid stepping on each other's toes? We'd have > to definitely 100% kill 'git push -f' and 'git rebase'. Also, would > patchwork help or hurt us here? I think Boris and I have been sort of > using it, but it's still got a pretty good backlog (partly real -- > i.e., the cause for this thread; and partly artificial, due to > accounting). patchwork should be a good start. We could also try the tip scripts used by the x86 maintainer team. https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/tree/.tip?h=tip > What to do about mtd-utils.git? That's been languishing a bit, and it > has no release schedule. Maybe we want a plan for that too. I'd volunteer to nurse it together with David Oberhollenzer. In fact, David is currently preparing a v2 pre-release of mtd-utils. https://github.com/sigma-star/mtd-utils/commits/wip_v2-rc1 We reworked a lot of code and added new tools. Thanks, //richard