All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, daniel@ffwll.ch
Subject: Re: [PATCH] kernel-doc: add support for asciidoc output
Date: Tue, 26 Jan 2016 13:22:31 +0200	[thread overview]
Message-ID: <87vb6gtwjs.fsf@intel.com> (raw)
In-Reply-To: <20160125164122.15fdedb3@lwn.net>

On Tue, 26 Jan 2016, Jonathan Corbet <corbet@lwn.net> wrote:
> On Mon, 18 Jan 2016 10:41:17 +0200
> Jani Nikula <jani.nikula@intel.com> 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

      reply	other threads:[~2016-01-26 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18  8:41 [PATCH] kernel-doc: add support for asciidoc output Jani Nikula
2016-01-25 23:41 ` Jonathan Corbet
2016-01-26 11:22   ` Jani Nikula [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vb6gtwjs.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=corbet@lwn.net \
    --cc=daniel@ffwll.ch \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.