From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932199AbcKRXlO (ORCPT ); Fri, 18 Nov 2016 18:41:14 -0500 Received: from ms.lwn.net ([45.79.88.28]:40132 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753025AbcKRXlK (ORCPT ); Fri, 18 Nov 2016 18:41:10 -0500 X-Greylist: delayed 476 seconds by postgrey-1.27 at vger.kernel.org; Fri, 18 Nov 2016 18:41:10 EST Date: Fri, 18 Nov 2016 16:33:12 -0700 From: Jonathan Corbet To: Takashi Iwai Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Jarkko Sakkinen , SeongJae Park Subject: Re: linux-next: manual merge of the sound tree with the jc_docs tree Message-ID: <20161118163312.46505e6f@lwn.net> In-Reply-To: References: <20161114111553.533d5615@canb.auug.org.au> <20161113175628.7906efa8@lwn.net> Organization: LWN.net X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 14 Nov 2016 09:01:13 +0100 Takashi Iwai wrote: > > In this case, I would have liked the chance to comment. This > > documentation belongs in the driver-api document, not the top-level one. > > So, in an ideal world, I'd like to see this stuff moved there, preferably > > with the patches going though the docs tree. > > If there needs any other changes, feel free to merge my > topic/restize-docs branch into yours and keep working there: > git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git topic/resize-docs OK, I've done that, so this series will show up in docs-next; hopefully the merge conflicts will be resolved in the process. I had said that I really wanted to move it all under driver-api and put it into that manual, but, looking at what's there, it's not that simple. The driver API parts of that manual belong there, but some of the information is user-oriented. A long-term goal is to separate out those two types of information so that interested readers can more easily find the information relevant to them. But that won't happen for 4.10..:) So I'll leave things as they are for now. (Note also that the driver API manual already has a section on sound devices: http://static.lwn.net/kerneldoc/driver-api/sound.html This came from the driver DocBook conversion a while back. At some point we should really pull all that stuff together into a single document). Thanks again for doing this conversion, jon