From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965206AbcAZLWg (ORCPT ); Tue, 26 Jan 2016 06:22:36 -0500 Received: from mga02.intel.com ([134.134.136.20]:50825 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932135AbcAZLWe (ORCPT ); Tue, 26 Jan 2016 06:22:34 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,350,1449561600"; d="scan'208";a="901321696" From: Jani Nikula To: Jonathan Corbet Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, daniel@ffwll.ch Subject: Re: [PATCH] kernel-doc: add support for asciidoc output In-Reply-To: <20160125164122.15fdedb3@lwn.net> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <1453106477-21359-1-git-send-email-jani.nikula@intel.com> <20160125164122.15fdedb3@lwn.net> User-Agent: Notmuch/0.21+34~g7dd0d52 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Tue, 26 Jan 2016 13:22:31 +0200 Message-ID: <87vb6gtwjs.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, 26 Jan 2016, Jonathan Corbet wrote: > On Mon, 18 Jan 2016 10:41:17 +0200 > Jani Nikula wrote: > >> Add new -asciidoc option to produce asciidoc output from kernel-doc. The >> output is formatted internally, with no dependencies on external >> tools. Any asciidoc formatting present in kernel-doc will naturally be >> present in the resulting asciidoc as well. > > As you may have seen, I took this and sort of ran with it - thanks! I'm > not sure I want to merge this functionality without an in-kernel user, but > we're on the way toward having that now. I'll reply to that thread shortly! >> I tested this mostly on drm/i915. I had to drop a few totally bogus >> kernel-doc comments for everything to work cleanly, series at >> http://patchwork.freedesktop.org/series/2581/. > > Aside from all of this, could I prevail upon you to submit those? They > are worth having regardless. They have all been merged to our tree, on their way upstream eventually. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center