From: <yanjiang.jin@windriver.com>
To: <horia.geanta@freescale.com>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>
Cc: <kim.phillips@freescale.com>, <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: [PATCH 0/3] fix some CAAM warnings.
Date: Tue, 3 Mar 2015 14:50:50 +0800 [thread overview]
Message-ID: <1425365453-19358-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.
The patches 0001 and 0002 are same as V1.
I have tested this on fsl-p5020ds board using upstream 4.0.0-rc1+ with the below configs:
CONFIG_DMA_API_DEBUG=y
# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
Change log:
v2:
Abandon the v1 patch 0003-crypto-caamhash-add-two-missed-dma_mapping_error.patch.
Replace the v1 patch 0004-crypto-caamhash-replace-kmalloc-with-kzalloc.patch with the new
patch 0003-crypto-caamhash-fix-uninitialized-edesc-sec4_sg_byte.patch.
Yanjiang Jin (3):
crypto: caam: fix some compile warnings
crypto: caam_rng: fix rng_unmap_ctx's DMA_UNMAP size problem
crypto: caamhash: - fix uninitialized edesc->sec4_sg_bytes field
drivers/crypto/caam/caamhash.c | 1 +
drivers/crypto/caam/caamrng.c | 4 ++--
drivers/crypto/caam/sg_sw_sec4.h | 8 ++++----
3 files changed, 7 insertions(+), 6 deletions(-)
--
1.9.1
next reply other threads:[~2015-03-03 6:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 6:50 yanjiang.jin [this message]
2015-03-03 6:50 ` [PATCH 1/3] crypto: caam: fix some compile warnings yanjiang.jin
2015-03-03 18:59 ` Kim Phillips
2015-03-04 2:32 ` yjin
2015-03-04 4:57 ` yjin
2015-03-04 9:03 ` Cristian Stoica
2015-03-04 18:34 ` Kim Phillips
2015-03-05 7:12 ` Cristian Stoica
2015-03-06 0:38 ` Kim Phillips
2015-03-04 8:48 ` Cristian Stoica
2015-03-04 9:11 ` Cristian Stoica
2015-03-03 6:50 ` [PATCH 2/3] crypto: caam_rng: fix rng_unmap_ctx's DMA_UNMAP size problem yanjiang.jin
2015-03-03 19:31 ` Kim Phillips
2015-03-04 5:33 ` yjin
2015-03-04 18:36 ` Kim Phillips
2015-03-05 2:52 ` yjin
2015-03-06 0:28 ` Kim Phillips
2015-03-03 6:50 ` [PATCH 3/3] crypto: caamhash: - fix uninitialized edesc->sec4_sg_bytes field yanjiang.jin
2015-03-03 13:39 ` [PATCH 0/3] fix some CAAM warnings Horia Geantă
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=1425365453-19358-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 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.