All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hook, Gary" <Gary.Hook@amd.com>
To: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>
Subject: [PATCH v2 0/2] Clean up crypto documentation
Date: Tue, 25 Jun 2019 23:43:36 +0000	[thread overview]
Message-ID: <156150616764.22527.16524544899486041609.stgit@taos> (raw)

Tidy up the crypto documentation by filling in some variable
descriptions, make some grammatical corrections, and enhance
formatting.

Changes since v1:
 - Remove patch with superfluous change to index (patch 2)
 - Remove unnecessary markup on function names in patch 3
 - Un-add extraneous white space (patch 3)

---

Gary R Hook (2):
      crypto: doc - Add parameter documentation
      crypto: doc - Fix formatting of new crypto engine content


 Documentation/crypto/api-skcipher.rst  |    2 -
 Documentation/crypto/crypto_engine.rst |  111 +++++++++++++++++++++-----------
 include/linux/crypto.h                 |   11 +++
 3 files changed, 85 insertions(+), 39 deletions(-)

--

             reply	other threads:[~2019-06-25 23:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 23:43 Hook, Gary [this message]
2019-06-25 23:43 ` [PATCH v2 1/2] crypto: doc - Add parameter documentation Hook, Gary
2019-06-25 23:43 ` [PATCH v2 2/2] crypto: doc - Fix formatting of new crypto engine content Hook, Gary
2019-06-26  0:13   ` Joe Perches
2019-06-26 16:50     ` Gary R Hook
2019-07-03 14:28 ` [PATCH v2 0/2] Clean up crypto documentation Herbert Xu

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=156150616764.22527.16524544899486041609.stgit@taos \
    --to=gary.hook@amd.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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 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.