mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Lendacky <thomas.lendacky@amd.com>
To: <davem@davemloft.net>, <linux-crypto@vger.kernel.org>,
	<herbert@gondor.apana.org.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] crypto: ccp - code fixes/cleanup
Date: Tue, 10 Dec 2013 10:38:27 -0600	[thread overview]
Message-ID: <20131210163827.24304.36256.stgit@tlendack-t1.amdoffice.net> (raw)

The following series implements fixes and cleanup for some reported
errors and suggestions (sparse errors, randconfig build errors and
pr_err usage).

This patch series is based on the cryptodev-2.6 kernel tree.

---

Tom Lendacky (3):
      crypto: ccp - Fix sparse warnings in ccp-crypto-sha.c
      crypto: ccp - CCP Kconfig fixes
      crypto: ccp - Remove user triggerable pr_err calls


 drivers/crypto/Kconfig                   |    2 +-
 drivers/crypto/ccp/Kconfig               |    1 +
 drivers/crypto/ccp/ccp-crypto-aes-cmac.c |    4 +---
 drivers/crypto/ccp/ccp-crypto-aes-xts.c  |   12 +++---------
 drivers/crypto/ccp/ccp-crypto-aes.c      |   12 +++---------
 drivers/crypto/ccp/ccp-crypto-sha.c      |    8 ++++----
 drivers/crypto/ccp/ccp-crypto.h          |    2 +-
 7 files changed, 14 insertions(+), 27 deletions(-)

-- 
Tom Lendacky


             reply	other threads:[~2013-12-10 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10 16:38 Tom Lendacky [this message]
2013-12-10 16:38 ` [PATCH 1/3] crypto: ccp - Fix sparse warnings in ccp-crypto-sha.c Tom Lendacky
2013-12-10 16:38 ` [PATCH 2/3] crypto: ccp - CCP Kconfig fixes Tom Lendacky
2013-12-10 16:38 ` [PATCH 3/3] crypto: ccp - Remove user triggerable pr_err calls Tom Lendacky
2013-12-20 14:07 ` [PATCH 0/3] crypto: ccp - code fixes/cleanup Herbert Xu

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=20131210163827.24304.36256.stgit@tlendack-t1.amdoffice.net \
    --to=thomas.lendacky@amd.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®