Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751702AbcLEMEe (ORCPT ); Mon, 5 Dec 2016 07:04:34 -0500 Received: from ec2-52-27-115-49.us-west-2.compute.amazonaws.com ([52.27.115.49]:43757 "EHLO osg.samsung.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750951AbcLEMDu (ORCPT ); Mon, 5 Dec 2016 07:03:50 -0500 Date: Mon, 5 Dec 2016 10:03:37 -0200 From: Mauro Carvalho Chehab To: Lukas Wunner Cc: "Rafael J. Wysocki" , Greg Kroah-Hartman , Jonathan Corbet , Silvio Fricke , "Luis R. Rodriguez" , Marek Szyprowski , Bartlomiej Zolnierkiewicz , Andrzej Hajda , Inki Dae , Joerg Roedel , Kukjin Kim , Krzysztof Kozlowski , Mark Brown , Tomeu Vizoso , Kevin Hilman , Ulf Hansson , Geert Uytterhoeven , Tobias Jakobi , Tomasz Figa , Grant Likely , Laurent Pinchart , Lars-Peter Clausen , Dmitry Torokhov , Christoph Hellwig , Arnd Bergmann , Alan Stern , Hanjun Guo , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, linux-samsung-soc@vger.kernel.org Subject: Re: [PATCH 0/2] Device links documentation Message-ID: <20161205100243.65b54d63@vento.lan> In-Reply-To: References: Organization: Samsung X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 942 Lines: 27 Hi Lukas, Em Sun, 4 Dec 2016 13:10:04 +0100 Lukas Wunner escreveu: > Here's my suggestion for initial documentation on the device links > feature that's queued for 4.10 on Greg KH's driver-core-next branch. > Please let me know if you have any additions or corrections. > > To read this in rendered form: > http://wunner.de/kernel-doc/core-api/device_link.html > > Patch [2/2] could go in via driver-core-next, but patch [1/2] would > need to go in via docs-next (because the core-api directory doesn't > exist yet in driver-core-next). > > @Jonathan Corbet: Is core-api the right place to put this? An > alternative would be Documentation/driver-api, but unlike core-api > it contains less prose text but mostly just bare API docs gleaned > from kernel-doc. Just my 2 cents here, but, IMHO, this belongs to driver-api. Yeah, it contains less prose, with is, IMHO, something that should be improved ;) Regards, Mauro