From: Randy Dunlap <rdunlap@infradead.org>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Stephan Mueller <smueller@chronox.de>
Cc: linux-crypto@vger.kernel.org, "'LKML'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: Documentation: remove colons in comments
Date: Tue, 20 Jan 2015 16:28:30 -0800 [thread overview]
Message-ID: <54BEF2AE.7050007@infradead.org> (raw)
In-Reply-To: <20150120034750.GB11274@gondor.apana.org.au>
On 01/19/15 19:47, Herbert Xu wrote:
> On Mon, Jan 19, 2015 at 12:13:39AM +0100, Stephan Mueller wrote:
>> As documented in Documentation/kernel-doc-nano-HOWTO.txt lines
>> terminated with a colon are treated as headings.
>>
>> The current layout of the documentation when compiling the kernel
>> crypto API DocBook documentation is messed up by by treating some lines
>> as headings. The patch removes colons from comments that shall not be
>> treated as headings.
>>
>> Signed-off-by: Stephan Mueller <smueller@chronox.de>
>
> Applied.
>
Ack. Thanks.
--
~Randy
prev parent reply other threads:[~2015-01-21 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 23:13 [PATCH] crypto: Documentation: remove colons in comments Stephan Mueller
2015-01-20 3:47 ` Herbert Xu
2015-01-21 0:28 ` Randy Dunlap [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=54BEF2AE.7050007@infradead.org \
--to=rdunlap@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox