From: Stephan Mueller <smueller@chronox.de>
To: linux-doc@vger.kernel.org
Cc: linux-crypto@vger.kernel.org
Subject: SPHINX: no structured comments
Date: Sat, 15 Oct 2016 17:05:51 +0200 [thread overview]
Message-ID: <1730886.FCUxIFiraa@positron.chronox.de> (raw)
Hi,
I am converting the kernel crypto API DocBook into Sphinx. The conversion is
complete, but I am having difficulties finding the cause for the following
notification obtained during the Sphinx compilation:
./include/linux/crypto.h:1: warning: no structured comments found
I am unsure what is wrong in line 1 of the mentioned header.
Thanks a lot
Stephan
next reply other threads:[~2016-10-15 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 15:05 Stephan Mueller [this message]
2016-10-15 16:12 ` SPHINX: no structured comments Markus Heiser
2016-10-15 22:12 ` 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=1730886.FCUxIFiraa@positron.chronox.de \
--to=smueller@chronox.de \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@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