linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Jonathan Corbet <corbet@lwn.net>,
	keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 02/18] docs: crypto: convert asymmetric-keys.txt to ReST
Date: Tue, 3 Mar 2020 22:09:28 +0200	[thread overview]
Message-ID: <20200303200928.GF5775@linux.intel.com> (raw)
In-Reply-To: <0e467df334fb6563a50190e0523a5ed1af1638ed.1583243826.git.mchehab+huawei@kernel.org>

On Tue, Mar 03, 2020 at 02:59:09PM +0100, Mauro Carvalho Chehab wrote:
> This file is almost compatible with ReST. Just minor changes
> were needed:
> 
> - Adjust document and titles markups;
> - Adjust numbered list markups;
> - Add a comments markup for the Contents section;
> - Add markups for literal blocks.
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>

Acked-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>

/Jarkko

  reply	other threads:[~2020-03-03 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1583243826.git.mchehab+huawei@kernel.org>
2020-03-03 13:59 ` [PATCH v3 02/18] docs: crypto: convert asymmetric-keys.txt to ReST Mauro Carvalho Chehab
2020-03-03 20:09   ` Jarkko Sakkinen [this message]
2020-03-03 13:59 ` [PATCH v3 03/18] docs: crypto: convert api-intro.txt to ReST format Mauro Carvalho Chehab
2020-03-03 13:59 ` [PATCH v3 04/18] docs: crypto: convert async-tx-api.txt " Mauro Carvalho Chehab
2020-03-06 13:38   ` Vinod Koul
2020-03-03 13:59 ` [PATCH v3 05/18] docs: crypto: descore-readme.txt: convert " Mauro Carvalho Chehab

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=20200303200928.GF5775@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=mchehab+huawei@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;
as well as URLs for NNTP newsgroup(s).