All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
	linux-doc@vger.kernel.org, Harsh Jain <harshjain.prof@gmail.com>
Subject: Re: [PATCH 7/7] crypto: doc - clarify AEAD memory structure
Date: Sun, 16 Oct 2016 15:20:03 +0200	[thread overview]
Message-ID: <1942120.Tqv0cleBQn@positron.chronox.de> (raw)
In-Reply-To: <62B7147E-395E-4615-AB9D-DA6B3E932FCD@darmarit.de>

Am Sonntag, 16. Oktober 2016, 15:11:38 CEST schrieb Markus Heiser:

Hi Markus,

> These are only my 2cent in hope that helps ... there is no rule
> to use any special markup ... use markup as you prefer ;-)

Thanks for the pointers. I will release a new patch set following your 
suggestions after others had the chance to review and comment.

Thanks!

Ciao
Stephan

      reply	other threads:[~2016-10-16 13:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-16  3:15 [PATCH 0/7] Conversion crypto API documentation to Sphinx Stephan Mueller
2016-10-16  3:16 ` [PATCH 1/7] crypto: doc - convert " Stephan Mueller
2016-10-16  3:17 ` [PATCH 2/7] crypto: doc - remove crypto API DocBook Stephan Mueller
2016-10-16  3:18 ` [PATCH 3/7] crypto: doc - fix source comments for Sphinx Stephan Mueller
2016-10-16 12:56   ` Markus Heiser
2016-10-16 13:03     ` Stephan Mueller
2016-10-16 13:42       ` Markus Heiser
2016-10-16  3:18 ` [PATCH 4/7] crypto: doc - fix separation of cipher / req API Stephan Mueller
2016-10-17 11:04   ` Jani Nikula
2016-10-17 12:35     ` Stephan Mueller
2016-10-17 13:20       ` Jani Nikula
2016-10-16  3:19 ` [PATCH 5/7] crypto: doc - add KPP documentation Stephan Mueller
2016-10-16  3:19 ` [PATCH 6/7] crypto: doc - remove crypto_alloc_ablkcipher Stephan Mueller
2016-10-16  3:22 ` [PATCH 7/7] crypto: doc - clarify AEAD memory structure Stephan Mueller
2016-10-16 13:11   ` Markus Heiser
2016-10-16 13:20     ` Stephan Mueller [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=1942120.Tqv0cleBQn@positron.chronox.de \
    --to=smueller@chronox.de \
    --cc=harshjain.prof@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=markus.heiser@darmarit.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 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.