From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from s3.sipsolutions.net ([2a01:4f8:190:3424::2] helo=sipsolutions.net) by bombadil.infradead.org with esmtps (Exim 4.87 #1 (Red Hat Linux)) id 1dBfuF-0006gq-VZ for linux-mtd@lists.infradead.org; Fri, 19 May 2017 11:17:18 +0000 Message-ID: <1495192604.3274.5.camel@sipsolutions.net> Subject: Re: [PATCH 08/29] rfkill.txt: standardize document format From: Johannes Berg To: Mauro Carvalho Chehab Cc: Linux Doc Mailing List , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Jonathan Corbet , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Richard Weinberger , Cyrille Pitchen , linux-mtd@lists.infradead.org, linux-wireless@vger.kernel.org Date: Fri, 19 May 2017 13:16:44 +0200 In-Reply-To: <20170519081117.6da0a699@vento.lan> References: <3361dce0e96427ed8fc375ab78371c0a6d0f55cc.1495157082.git.mchehab@s-opensource.com> <1495188901.3274.0.camel@sipsolutions.net> <20170519081117.6da0a699@vento.lan> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 2017-05-19 at 08:11 -0300, Mauro Carvalho Chehab wrote: > > Yes, it should work. Actually, you would need to use :depth: 2 to > produce this output: > > > Contents > >     . rfkill - RF kill switch support >         . Introduction >         . Implementation details >         . Kernel API >         . Userspace support Sounds good to me. > I opted to keep the contents as a comment just because, in the past, > some maintainers complained about TOC removal, arguing that it makes > harder for the ones that would be reading the file in ascii. Ok. I don't really care much either way, I guess. The file is short enough that the TOC isn't all that important to start with. johannes