From: fabio.baltieri@linaro.org (Fabio Baltieri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] Various ux500 crypto updates
Date: Tue, 25 Jun 2013 10:54:43 +0200 [thread overview]
Message-ID: <1372150489-25594-1-git-send-email-fabio.baltieri@linaro.org> (raw)
Hello Herbert,
these are some fixes to issue pointed out by sparse and dmaengine API
udpates on the recently enabled ux500 hw crypto drivers.
These are based on recent linux-next, and can probably be applied on an
architecture specific branch with your ack, or just skip to the next
merge window.
Thanks,
Fabio
Fabio Baltieri (6):
crypto: ux500/hash: use readl on iomem addresses
crypto: ux500/hash: add missing static qualifiers
crypto: ux500/crypt: add missing __iomem qualifiers
crypto: ux500: use dmaengine_device_control API
crypto: ux500: use dmaengine_prep_slave_sg API
crypto: ux500: use dmaengine_submit API
drivers/crypto/ux500/cryp/cryp.c | 4 ++--
drivers/crypto/ux500/cryp/cryp_core.c | 26 +++++++++++++-------------
drivers/crypto/ux500/hash/hash_core.c | 33 ++++++++++++++++-----------------
3 files changed, 31 insertions(+), 32 deletions(-)
--
1.8.2
next reply other threads:[~2013-06-25 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 8:54 Fabio Baltieri [this message]
2013-06-25 8:54 ` [PATCH 1/6] crypto: ux500/hash: use readl on iomem addresses Fabio Baltieri
2013-06-25 8:54 ` [PATCH 2/6] crypto: ux500/hash: add missing static qualifiers Fabio Baltieri
2013-06-25 8:54 ` [PATCH 3/6] crypto: ux500/crypt: add missing __iomem qualifiers Fabio Baltieri
2013-06-25 8:54 ` [PATCH 4/6] crypto: ux500: use dmaengine_device_control API Fabio Baltieri
2013-06-25 8:54 ` [PATCH 5/6] crypto: ux500: use dmaengine_prep_slave_sg API Fabio Baltieri
2013-06-25 8:54 ` [PATCH 6/6] crypto: ux500: use dmaengine_submit API Fabio Baltieri
2013-06-25 9:20 ` [PATCH 0/6] Various ux500 crypto updates Linus Walleij
2013-06-25 11:17 ` Herbert Xu
2013-06-25 12:34 ` Linus Walleij
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=1372150489-25594-1-git-send-email-fabio.baltieri@linaro.org \
--to=fabio.baltieri@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).