From: Stephan Mueller <smueller@chronox.de>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 3/7] crypto: doc - fix source comments for Sphinx
Date: Sun, 16 Oct 2016 15:03:45 +0200 [thread overview]
Message-ID: <2972819.9tl40PCxdP@positron.chronox.de> (raw)
In-Reply-To: <0255D43E-2C6A-4630-9F86-9723366188EC@darmarit.de>
Am Sonntag, 16. Oktober 2016, 14:56:49 CEST schrieb Markus Heiser:
Hi Markus,
...
> compared to DocBook, with sphinx you can use (have to use) the reST markup
> in source code comments.
>
> Here, the code example is just a (indented) float text and this is
> why you have to quote the asterisk "\*req,".
Is there any preferred / suggested way whether to use literal or highlighted
(or even my approach on) formatting?
Ciao
Stephan
next prev parent reply other threads:[~2016-10-16 13:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 3:15 [PATCH 0/7] Conversion crypto API documentation to Sphinx Stephan Mueller
2016-10-16 3:16 ` [PATCH 1/7] crypto: doc - convert " Stephan Mueller
2016-10-16 3:17 ` [PATCH 2/7] crypto: doc - remove crypto API DocBook Stephan Mueller
2016-10-16 3:18 ` [PATCH 3/7] crypto: doc - fix source comments for Sphinx Stephan Mueller
2016-10-16 12:56 ` Markus Heiser
2016-10-16 13:03 ` Stephan Mueller [this message]
2016-10-16 13:42 ` Markus Heiser
2016-10-16 3:18 ` [PATCH 4/7] crypto: doc - fix separation of cipher / req API Stephan Mueller
2016-10-17 11:04 ` Jani Nikula
2016-10-17 12:35 ` Stephan Mueller
2016-10-17 13:20 ` Jani Nikula
2016-10-16 3:19 ` [PATCH 5/7] crypto: doc - add KPP documentation Stephan Mueller
2016-10-16 3:19 ` [PATCH 6/7] crypto: doc - remove crypto_alloc_ablkcipher Stephan Mueller
2016-10-16 3:22 ` [PATCH 7/7] crypto: doc - clarify AEAD memory structure Stephan Mueller
2016-10-16 13:11 ` Markus Heiser
2016-10-16 13:20 ` Stephan Mueller
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=2972819.9tl40PCxdP@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
/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.