From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752579AbdLKVwm (ORCPT ); Mon, 11 Dec 2017 16:52:42 -0500 Received: from ms.lwn.net ([45.79.88.28]:55826 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751813AbdLKVwk (ORCPT ); Mon, 11 Dec 2017 16:52:40 -0500 Date: Mon, 11 Dec 2017 14:52:39 -0700 From: Jonathan Corbet To: Peter Rosin Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH 0/2] mux: add overview and add to driver-api docs Message-ID: <20171211145239.25455568@lwn.net> In-Reply-To: <20171211082943.5796-1-peda@axentia.se> References: <20171211082943.5796-1-peda@axentia.se> Organization: LWN.net 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, 11 Dec 2017 09:29:41 +0100 Peter Rosin wrote: > Don't know if this is worth adding, but it might answer at least a few > questions. > > It looks ok when I view the htmldocs output, but I'm not all that certain > this is good to go? Almost, but I have one request: the new mux.rst file is rather unenlightening for somebody who reads it directly in the docs tree. If you want to keep the bulk of the text in the source I can live with that, but can mux.rst at least get an introductory paragraph saying what it covers (what *is* the mux subsystem?) and why readers might want to go find the rest? Thanks, jon