From: Richard Hartmann <richih.mailinglist@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: Richard Hartmann <richih.mailinglist@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: [PATCH 07/19] crypto: seed - Fix checkpatch errors
Date: Fri, 19 Feb 2010 01:22:18 +0100 [thread overview]
Message-ID: <1266538939-3311-1-git-send-email-richih.mailinglist@gmail.com> (raw)
Signed-off-by: Richard Hartmann <richih.mailinglist@gmail.com>
---
crypto/seed.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/crypto/seed.c b/crypto/seed.c
index d3e422f..3c0afae 100644
--- a/crypto/seed.c
+++ b/crypto/seed.c
@@ -329,7 +329,7 @@ static const u32 KC[SEED_NUM_KCONSTANTS] = {
X2 ^= t1;
static int seed_set_key(struct crypto_tfm *tfm, const u8 *in_key,
- unsigned int key_len)
+ unsigned int key_len)
{
struct seed_ctx *ctx = crypto_tfm_ctx(tfm);
u32 *keyout = ctx->keysched;
--
1.6.6.1
reply other threads:[~2010-02-19 0:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1266538939-3311-1-git-send-email-richih.mailinglist@gmail.com \
--to=richih.mailinglist@gmail.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;
as well as URLs for NNTP newsgroup(s).