From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jonathan Corbet <corbet@lwn.net>
Subject: Re: Generic kernel features that need architecture(mips) support
Date: Thu, 11 Jun 2015 07:20:28 -0600
Message-ID: <20150611072028.7d0fe2d7@lwn.net>
References: <55759543.1010408@gmail.com>
	<20150610145804.GG2753@linux-mips.org>
	<5578679D.2030307@gmail.com>
	<20150611062452.GB32133@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Return-path: <linux-arch-owner@vger.kernel.org>
In-Reply-To: <20150611062452.GB32133@gmail.com>
Sender: linux-arch-owner@vger.kernel.org
To: Ingo Molnar <mingo@kernel.org>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>, Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org, linux-arch@vger.kernel.org, linux-api@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
List-Id: linux-api@vger.kernel.org

On Thu, 11 Jun 2015 08:24:53 +0200
Ingo Molnar <mingo@kernel.org> wrote:

> Jon: would you like to receive all patches to Documentation/features/=
 so you can=20
> collect them in the documentation tree, or can maintainers patch it a=
s part of any=20
> feature work that affects the tables? I think it's all finegrained en=
ough to not=20
> create conflicts. That way they would become partly self-maintaining.=
 (Or at least=20
> one can always hope! ;-)

I sort of figured I'd handle it the way I do the rest of Documentation/=
 =E2=80=94
I'm happy to herd the patches, but I also have no problem staying out o=
f
the way when other maintainers reach into it.

jon