From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephan Mueller <smueller@chronox.de>
Subject: Re: [PATCH 3/7] crypto: doc - fix source comments for Sphinx
Date: Sun, 16 Oct 2016 15:03:45 +0200
Message-ID: <2972819.9tl40PCxdP@positron.chronox.de>
References: <2721226.4nLlHD9uQ6@positron.chronox.de> <2601538.cyVHbpjp9L@positron.chronox.de> <0255D43E-2C6A-4630-9F86-9723366188EC@darmarit.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
        linux-doc@vger.kernel.org
To: Markus Heiser <markus.heiser@darmarit.de>
Return-path: <linux-doc-owner@vger.kernel.org>
In-Reply-To: <0255D43E-2C6A-4630-9F86-9723366188EC@darmarit.de>
Sender: linux-doc-owner@vger.kernel.org
List-Id: linux-crypto.vger.kernel.org

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