Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754582AbbFKNSC (ORCPT ); Thu, 11 Jun 2015 09:18:02 -0400 Received: from tex.lwn.net ([70.33.254.29]:41144 "EHLO vena.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752647AbbFKNRx (ORCPT ); Thu, 11 Jun 2015 09:17:53 -0400 Date: Thu, 11 Jun 2015 07:20:28 -0600 From: Jonathan Corbet To: Ingo Molnar Cc: Xose Vazquez Perez , Ralf Baechle , linux-mips@linux-mips.org, linux-arch@vger.kernel.org, linux-api@vger.kernel.org, LKML Subject: Re: Generic kernel features that need architecture(mips) support Message-ID: <20150611072028.7d0fe2d7@lwn.net> In-Reply-To: <20150611062452.GB32133@gmail.com> References: <55759543.1010408@gmail.com> <20150610145804.GG2753@linux-mips.org> <5578679D.2030307@gmail.com> <20150611062452.GB32133@gmail.com> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 887 Lines: 19 On Thu, 11 Jun 2015 08:24:53 +0200 Ingo Molnar wrote: > Jon: would you like to receive all patches to Documentation/features/ so you can > collect them in the documentation tree, or can maintainers patch it as part of any > feature work that affects the tables? I think it's all finegrained enough to not > create conflicts. That way they would become partly self-maintaining. (Or at least > one can always hope! ;-) I sort of figured I'd handle it the way I do the rest of Documentation/ — I'm happy to herd the patches, but I also have no problem staying out of the way when other maintainers reach into it. jon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/