From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: [PULL] One more documentation update for 4.10
Date: Fri, 16 Dec 2016 10:30:56 -0700 [thread overview]
Message-ID: <20161216103056.62971a62@lwn.net> (raw)
The following changes since commit
868c97a846a73e937d835b09b8c885a69df50ec8:
dma-buf: Extract dma-buf.rst (2016-12-11 13:37:55 -0700)
are available in the git repository at:
git://git.lwn.net/linux.git tags/docs-4.10-2
for you to fetch changes up to 3fa71d0f58a9b9df84e8e79196f961bcfbf01b2e:
crypto: doc - optimize compilation (2016-12-13 16:38:07 -0700)
----------------------------------------------------------------
This pull contains one set of changes: a conversion of the crypto DocBook
to Sphinx.
This work was ready in October, but, due to some miscommunication, didn't
make it into my tree. It reaches into the crypto subsystem to update
various kerneldoc comments; I don't have a formal ack from Herbert for
that, but I figure that his "no objections from me" is good enough to go
with.
----------------------------------------------------------------
Stephan Mueller (8):
crypto: doc - convert crypto API documentation to Sphinx
crypto: doc - remove crypto API DocBook
crypto: doc - fix source comments for Sphinx
crypto: doc - fix separation of cipher / req API
crypto: doc - add KPP documentation
crypto: doc - remove crypto_alloc_ablkcipher
crypto: doc - clarify AEAD memory structure
crypto: doc - optimize compilation
Documentation/DocBook/Makefile | 2 +-
Documentation/DocBook/crypto-API.tmpl | 2092 ---------------------------------
Documentation/crypto/api-aead.rst | 23 +
Documentation/crypto/api-akcipher.rst | 20 +
Documentation/crypto/api-digest.rst | 35 +
Documentation/crypto/api-kpp.rst | 38 +
Documentation/crypto/api-rng.rst | 14 +
Documentation/crypto/api-samples.rst | 224 ++++
Documentation/crypto/api-skcipher.rst | 62 +
Documentation/crypto/api.rst | 25 +
Documentation/crypto/architecture.rst | 441 +++++++
Documentation/crypto/devel-algos.rst | 247 ++++
Documentation/crypto/index.rst | 24 +
Documentation/crypto/intro.rst | 74 ++
Documentation/crypto/userspace-if.rst | 387 ++++++
Documentation/index.rst | 1 +
crypto/algif_aead.c | 14 +-
include/crypto/aead.h | 50 +-
include/crypto/dh.h | 58 +
include/crypto/ecdh.h | 58 +
include/crypto/hash.h | 2 +-
include/crypto/kpp.h | 15 +-
include/crypto/skcipher.h | 4 +-
include/linux/crypto.h | 4 +-
24 files changed, 1770 insertions(+), 2144 deletions(-)
delete mode 100644 Documentation/DocBook/crypto-API.tmpl
create mode 100644 Documentation/crypto/api-aead.rst
create mode 100644 Documentation/crypto/api-akcipher.rst
create mode 100644 Documentation/crypto/api-digest.rst
create mode 100644 Documentation/crypto/api-kpp.rst
create mode 100644 Documentation/crypto/api-rng.rst
create mode 100644 Documentation/crypto/api-samples.rst
create mode 100644 Documentation/crypto/api-skcipher.rst
create mode 100644 Documentation/crypto/api.rst
create mode 100644 Documentation/crypto/architecture.rst
create mode 100644 Documentation/crypto/devel-algos.rst
create mode 100644 Documentation/crypto/index.rst
create mode 100644 Documentation/crypto/intro.rst
create mode 100644 Documentation/crypto/userspace-if.rst
reply other threads:[~2016-12-16 17:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20161216103056.62971a62@lwn.net \
--to=corbet@lwn.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).