From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Ofir Drang <ofir.drang@arm.com>
Subject: [PATCH v3 0/6] staging: ccree: bug fixes and TODO items for 4.13
Date: Sun, 25 Jun 2017 10:47:18 +0300 [thread overview]
Message-ID: <1498376846-24136-1-git-send-email-gilad@benyossef.com> (raw)
An assortment of bug fixes and staging TODO items.
Highlights includes the driver passing crypto testmgr boot tests
and relying on device tree for various HW config options as
opposed to build time configuration.
CC: Dan Carpenter <dan.carpenter@oracle.com>
Gilad Ben-Yossef (6):
staging: ccree: fix hash import/export
staging: ccree: register setkey for none hash macs
staging: ccree: remove unused function
staging: ccree: add clock management support
staging: ccree: add DT bus coherency detection
staging: ccree: use signal safe completion wait
Changes from v2:
- Rebased on latest staging-next.
- Added poison of unused hash import field based
on review discussions with Dan Carpenter.
- Dropped older HW support patches for staging
at GregKH request.
- Rewrote for clarity hash setkey fix commit
message.
- Added now no longer needed KConfig option to
code dropped by bus coherency being set by DT
patch.
Changes from v1:
- Rebased on top of latest patches sent to mailing
list but not yet marged for same driver.
- Address Dan Carpenter style review comments
- Fix clk de-init being called on clk init failure
error path pointed out by Dan Carpenter.
drivers/staging/ccree/Kconfig | 9 --
drivers/staging/ccree/Makefile | 2 +-
drivers/staging/ccree/cc_hw_queue_defs.h | 12 --
drivers/staging/ccree/ssi_buffer_mgr.c | 37 ++---
drivers/staging/ccree/ssi_config.h | 20 ---
drivers/staging/ccree/ssi_driver.c | 55 ++++++--
drivers/staging/ccree/ssi_driver.h | 8 +-
drivers/staging/ccree/ssi_hash.c | 226 +++++++++++++++++++------------
drivers/staging/ccree/ssi_hash.h | 2 +
drivers/staging/ccree/ssi_pm.c | 13 +-
drivers/staging/ccree/ssi_pm_ext.c | 60 --------
drivers/staging/ccree/ssi_pm_ext.h | 33 -----
drivers/staging/ccree/ssi_request_mgr.c | 3 +-
13 files changed, 227 insertions(+), 253 deletions(-)
delete mode 100644 drivers/staging/ccree/ssi_pm_ext.c
delete mode 100644 drivers/staging/ccree/ssi_pm_ext.h
--
2.1.4
next reply other threads:[~2017-06-25 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 7:47 Gilad Ben-Yossef [this message]
2017-06-25 7:47 ` [PATCH v3 1/6] staging: ccree: fix hash import/export Gilad Ben-Yossef
2017-06-25 7:47 ` [PATCH v3 2/6] staging: ccree: register setkey for none hash macs Gilad Ben-Yossef
2017-06-25 7:47 ` [PATCH v3 3/6] staging: ccree: remove unused function Gilad Ben-Yossef
2017-06-25 7:47 ` [PATCH v3 4/6] staging: ccree: add clock management support Gilad Ben-Yossef
2017-06-25 7:47 ` [PATCH v3 5/6] staging: ccree: add DT bus coherency detection Gilad Ben-Yossef
2017-06-25 7:47 ` [PATCH v3 6/6] staging: ccree: use signal safe completion wait Gilad Ben-Yossef
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=1498376846-24136-1-git-send-email-gilad@benyossef.com \
--to=gilad@benyossef.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ofir.drang@arm.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