mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <yanjiang.jin@windriver.com>
To: <horia.geanta@freescale.com>, <herbert@gondor.apana.org.au>,
	<davem@davemloft.net>, <kim.phillips@freescale.com>
Cc: <ruchika.gupta@freescale.com>, <cristian.stoica@freescale.com>,
	<NiteshNarayanLal@freescale.com>, <linux-crypto@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <jinyanjiang@gmail.com>
Subject: [V3 PATCH 0/2]  fix some CAAM warnings.
Date: Fri, 6 Mar 2015 10:34:40 +0800	[thread overview]
Message-ID: <1425609282-16568-1-git-send-email-yanjiang.jin@windriver.com> (raw)

From: Yanjiang Jin <yanjiang.jin@windriver.com>

Hi,

This patch series fix some CAAM compile and runtime warnings.

I have tested this on fsl-p5020ds board using upstream 4.0.0-rc2 with the below configs:

CONFIG_DMA_API_DEBUG=y
# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set

Change log:
v3:

0001-crypto-caamhash-fix-uninitialized-edesc-sec4_sg_byte.patch is same as before.

For 0002-crypto-caam_rng-fix-rng_unmap_ctx-s-DMA_UNMAP-size-p.patch
1. Fix an alignment issue;
2. update DESC_RNG_LEN to (4 * CAAM_CMD_SZ).

Abandon the v2 patch 0001-crypto-caam-fix-some-compile-warnings.patch.

Yanjiang Jin (2):
  crypto: caamhash: - fix uninitialized edesc->sec4_sg_bytes field
  crypto: caam_rng: fix rng_unmap_ctx's DMA_UNMAP size problem

 drivers/crypto/caam/caamhash.c | 1 +
 drivers/crypto/caam/caamrng.c  | 6 +++---
 2 files changed, 4 insertions(+), 3 deletions(-)

-- 
1.9.1


             reply	other threads:[~2015-03-06  2:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06  2:34 yanjiang.jin [this message]
2015-03-06  2:34 ` [PATCH 1/2] crypto: caamhash: - fix uninitialized edesc->sec4_sg_bytes field yanjiang.jin
2015-03-07  0:36   ` Kim Phillips
2015-03-06  2:34 ` [PATCH 2/2] crypto: caam_rng: fix rng_unmap_ctx's DMA_UNMAP size problem yanjiang.jin
2015-03-07  0:37   ` Kim Phillips
2015-03-09 10:07 ` [V3 PATCH 0/2] fix some CAAM warnings 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=1425609282-16568-1-git-send-email-yanjiang.jin@windriver.com \
    --to=yanjiang.jin@windriver.com \
    --cc=NiteshNarayanLal@freescale.com \
    --cc=cristian.stoica@freescale.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@freescale.com \
    --cc=jinyanjiang@gmail.com \
    --cc=kim.phillips@freescale.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ruchika.gupta@freescale.com \
    /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
all inboxes | Powered by JetHome®