From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 3600E8FC for ; Fri, 29 Jul 2016 10:59:53 +0000 (UTC) Received: from galahad.ideasonboard.com (galahad.ideasonboard.com [185.26.127.97]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AD7C2276 for ; Fri, 29 Jul 2016 10:59:52 +0000 (UTC) From: Laurent Pinchart To: ksummit-discuss@lists.linuxfoundation.org Date: Fri, 29 Jul 2016 14:00:04 +0300 Message-ID: <44550834.xrXSv8h38b@avalon> In-Reply-To: <20160720171026.7d9d2c2b@lwn.net> References: <20160720171026.7d9d2c2b@lwn.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: Markus Heiser , Mauro Carvalho Chehab , "Nikula, Jani" , Grant Likely Subject: Re: [Ksummit-discuss] [TECH TOPIC] kernel documentation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wednesday 20 Jul 2016 17:10:26 Jonathan Corbet wrote: > On Wed, 20 Jul 2016 13:56:31 +0200 Daniel Vetter wrote: > > I think it'd be great if interested parties (might be just a hallway > > track) sit together and figure out how to best go about converting all > > the existing docs over, and how to link it all together. > > I had thought about proposing a similar topic. I think it could also be > useful to have a brief session on how the new stuff works. I'd be more interested in that than in a session that discusses the process of converting existing documentation. It's up to each subsystem to move away from DocBook, I don't really see what we would have to discuss there. That being said, in order to make the documentation consistent, we'll need some level of bikeshedding to decide on guidelines for maintainers and developers. I don't want to spend the kernel summit bikeshedding, but maybe a high-level discussion on what we need could be useful. -- Regards, Laurent Pinchart