linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: linux-crypto@vger.kernel.org
Cc: Marek Vasut <marex@denx.de>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Horia Geanta <horia.geanta@freescale.com>
Subject: [PATCH 00/11] crypto: caam: Error reporting fixes
Date: Thu, 24 Apr 2014 20:05:11 +0200	[thread overview]
Message-ID: <1398362722-16430-1-git-send-email-marex@denx.de> (raw)

First stab at reworking the error.c thing in Freescale CAAM.
This patchset cleans it up so it's not doing any too insane
string messing anymore.

NOTE: Can someone please test this on real hardware? I have
      none at hand, so THIS IS COMPILE-TESTED ONLY!

Marek Vasut (11):
  crypto: caam: Contain caam_jr_strstatus() ugliness
  crypto: caam: Pull all the error codes out
  crypto: caam: Implement fast-path for error codes with no handler
  crypto: caam: Pass error type into the functions
  crypto: caam: Kill the easy targets
  crypto: caam: Dissolve report_jump_idx()
  crypto: caam: Clean up report_ccb_status()
  crypto: caam: Clean up report_deco_status()
  crypto: caam: Kill SPRINTFCAT() with fire
  crypto: caam: Sweep the remnants
  crypto: caam: Fix the 'quoted string split across lines'

 drivers/crypto/caam/caamalg.c  |  28 +--
 drivers/crypto/caam/caamhash.c |  28 +--
 drivers/crypto/caam/caamrng.c  |   7 +-
 drivers/crypto/caam/error.c    | 389 +++++++++++++++++++----------------------
 drivers/crypto/caam/error.h    |   2 +-
 drivers/crypto/caam/key_gen.c  |   7 +-
 6 files changed, 200 insertions(+), 261 deletions(-)

Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Horia Geanta <horia.geanta@freescale.com>

-- 
1.9.2

             reply	other threads:[~2014-04-24 18:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 18:05 Marek Vasut [this message]
2014-04-24 18:05 ` [PATCH 01/11] crypto: caam: Contain caam_jr_strstatus() ugliness Marek Vasut
2014-04-24 18:05 ` [PATCH 02/11] crypto: caam: Pull all the error codes out Marek Vasut
2014-04-24 18:05 ` [PATCH 03/11] crypto: caam: Implement fast-path for error codes with no handler Marek Vasut
2014-04-24 18:05 ` [PATCH 04/11] crypto: caam: Pass error type into the functions Marek Vasut
2014-04-24 18:05 ` [PATCH 05/11] crypto: caam: Kill the easy targets Marek Vasut
2014-04-24 18:05 ` [PATCH 06/11] crypto: caam: Dissolve report_jump_idx() Marek Vasut
2014-04-24 18:05 ` [PATCH 07/11] crypto: caam: Clean up report_ccb_status() Marek Vasut
2014-04-24 18:05 ` [PATCH 08/11] crypto: caam: Clean up report_deco_status() Marek Vasut
2014-04-24 18:05 ` [PATCH 09/11] crypto: caam: Kill SPRINTFCAT() with fire Marek Vasut
2014-04-24 18:05 ` [PATCH 10/11] crypto: caam: Sweep the remnants Marek Vasut
2014-04-24 18:05 ` [PATCH 11/11] crypto: caam: Fix the 'quoted string split across lines' Marek Vasut
2014-04-25 18:20 ` [PATCH 00/11] crypto: caam: Error reporting fixes Kees Cook
2014-05-08 14:01 ` Herbert Xu
2014-05-08 14:50   ` Marek Vasut

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=1398362722-16430-1-git-send-email-marex@denx.de \
    --to=marex@denx.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@freescale.com \
    --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 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).