public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/9] kernel-doc/docproc prep work for reStructuredText
Date: Thu, 12 May 2016 16:15:35 +0300	[thread overview]
Message-ID: <cover.1463058396.git.jani.nikula@intel.com> (raw)

Jon, I was hoping we could consider nudging things forward a bit in the
kernel-doc and docproc reStructuredText front already in 4.7. I know
it's a bit close to the merge window, but this should not interfere with
anything else, and some of it are just trivial cleanups that I've been
carrying around locally.

Obviously this doesn't actually add anything that uses them yet, but I
think it would be helpful to have some common base in to ease
collaboration.

BR,
Jani.


Jani Nikula (8):
  kernel-doc: rewrite usage description, remove duplicated comments
  kernel-doc: use rst C domain directives and references for types
  docproc: add variables for subcommand and filename
  docproc: reduce unnecessary indentation
  docproc: abstract docproc directive detection
  docproc: abstract terminating lines at first space
  docproc: add support for reStructuredText format via --rst option
  docproc: print a comment about autogeneration for rst output

Jonathan Corbet (1):
  kernel-doc: produce RestructuredText output

 scripts/docproc.c  | 221 +++++++++++++++++++++++++++----------
 scripts/kernel-doc | 315 +++++++++++++++++++++++++++++++++++++++++++++--------
 2 files changed, 430 insertions(+), 106 deletions(-)

-- 
2.1.4

             reply	other threads:[~2016-05-12 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 13:15 Jani Nikula [this message]
2016-05-12 13:15 ` [PATCH 1/9] kernel-doc: rewrite usage description, remove duplicated comments Jani Nikula
2016-05-12 13:15 ` [PATCH 2/9] kernel-doc: produce RestructuredText output Jani Nikula
2016-05-12 13:15 ` [PATCH 3/9] kernel-doc: use rst C domain directives and references for types Jani Nikula
2016-05-12 13:15 ` [PATCH 4/9] docproc: add variables for subcommand and filename Jani Nikula
2016-05-12 13:15 ` [PATCH 5/9] docproc: reduce unnecessary indentation Jani Nikula
2016-05-12 13:15 ` [PATCH 6/9] docproc: abstract docproc directive detection Jani Nikula
2016-05-12 13:15 ` [PATCH 7/9] docproc: abstract terminating lines at first space Jani Nikula
2016-05-12 13:15 ` [PATCH 8/9] docproc: add support for reStructuredText format via --rst option Jani Nikula
2016-05-12 13:15 ` [PATCH 9/9] docproc: print a comment about autogeneration for rst output Jani Nikula
2016-05-14 16:01 ` [PATCH 0/9] kernel-doc/docproc prep work for reStructuredText Jonathan Corbet

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=cover.1463058396.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=corbet@lwn.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox