From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757378AbcIMNp6 (ORCPT ); Tue, 13 Sep 2016 09:45:58 -0400 Received: from mga09.intel.com ([134.134.136.24]:5706 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751633AbcIMNpz (ORCPT ); Tue, 13 Sep 2016 09:45:55 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,328,1470726000"; d="scan'208";a="1055333512" From: Jani Nikula To: Shuah Khan , Jonathan Corbet Cc: richardcochran@gmail.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-kselftest@vger.kernel.org, Shuah Khan , Markus Heiser Subject: Re: [PATCH 0/9] Move runnable code (tests) from Documentation to selftests In-Reply-To: <235dbbac-4950-9631-908a-b2dfbbd06def@osg.samsung.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20160910010100.72f1a9c4@lwn.net> <87sht4tav2.fsf@intel.com> <235dbbac-4950-9631-908a-b2dfbbd06def@osg.samsung.com> User-Agent: Notmuch/0.22.1+62~g2a7b11b (https://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Tue, 13 Sep 2016 16:45:44 +0300 Message-ID: <87eg4n29rr.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 13 Sep 2016, Shuah Khan wrote: > On 09/13/2016 03:20 AM, Jani Nikula wrote: >> FWIW, I'm in favor of moving *all* the code away from Documentation, not >> just tests. Essentially removing the CONFIG_BUILD_DOCSRC config option, >> and reserving Documentation/Makefile for documentation build. After this >> series, some of the remaining code belongs under samples, some under >> tools. > > I am planning another patch series to move all the examples and samples > and tools to their right location. Great! >> We could make it possible to include the code samples from samples into >> the Sphinx built documentation. > > I can't say I understand Sphinx, however, it might make sense to include > samples into Sphinx build. Is this approach different from the way they > are built under Documentation via Doc Makfiles now? It's just that by default Sphinx won't allow including files outside of its root directory, which is Documentation in this case. It just needs an extension for this. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center