From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-crypto@vger.kernel.org
Cc: "Horia Geantă" <horia.geanta@nxp.com>,
kernel@pengutronix.de, "Sascha Hauer" <s.hauer@pengutronix.de>
Subject: [PATCH 0/3] crypto: CAAM: Print debug messages at debug level
Date: Fri, 17 May 2019 11:29:02 +0200 [thread overview]
Message-ID: <20190517092905.1264-1-s.hauer@pengutronix.de> (raw)
The CAAM driver has most of its debug messages inside #ifdef DEBUG and
then prints them at KERN_ERR level. Do this properly and print the
messages at DEBUG_LEVEL as they are supposed to. With this we can get
rid of a lot of ifdefs in the code.
Sascha
Sascha Hauer (3):
crypto: caam: remove unused defines
crypto: caam: print debug messages at debug level
crypto: caam: print messages in caam_dump_sg at debug level
drivers/crypto/caam/caamalg.c | 110 ++++++++---------------
drivers/crypto/caam/caamalg_desc.c | 71 ++++-----------
drivers/crypto/caam/caamalg_qi.c | 38 +++-----
drivers/crypto/caam/caamalg_qi2.c | 4 +-
drivers/crypto/caam/caamhash.c | 134 +++++++++--------------------
drivers/crypto/caam/caamrng.c | 16 ++--
drivers/crypto/caam/error.c | 6 +-
drivers/crypto/caam/error.h | 2 +-
drivers/crypto/caam/key_gen.c | 19 ++--
drivers/crypto/caam/sg_sw_sec4.h | 5 +-
10 files changed, 124 insertions(+), 281 deletions(-)
--
2.20.1
next reply other threads:[~2019-05-17 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 9:29 Sascha Hauer [this message]
2019-05-17 9:29 ` [PATCH 1/3] crypto: caam: remove unused defines Sascha Hauer
2019-05-21 14:23 ` Horia Geanta
2019-05-17 9:29 ` [PATCH 2/3] crypto: caam: print debug messages at debug level Sascha Hauer
2019-05-17 9:50 ` Sascha Hauer
2019-05-21 14:18 ` Horia Geanta
2019-05-21 14:31 ` Horia Geanta
2019-05-17 9:29 ` [PATCH 3/3] crypto: caam: print messages in caam_dump_sg " Sascha Hauer
2019-05-21 14:33 ` Horia Geanta
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=20190517092905.1264-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=horia.geanta@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-crypto@vger.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 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.