From: Domen Puncer <domen@coderock.org>
To: herbert@gondor.apana.org.au
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org, adobriyan@mail.ru
Subject: Re: [patch 4/4 with proper signed-off] crypto/tea.c: fix sparse warnings
Date: Sun, 20 Mar 2005 12:21:17 +0100 [thread overview]
Message-ID: <20050320112117.GK14273@nd47.coderock.org> (raw)
In-Reply-To: <20050319131819.9B87C1ECA8@trashy.coderock.org>
Signed-off-by: Alexey Dobriyan <adobriyan@mail.ru>
Signed-off-by: Domen Puncer <domen@coderock.org>
---
kj-domen/crypto/tea.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -puN crypto/tea.c~sparse-crypto_tea crypto/tea.c
--- kj/crypto/tea.c~sparse-crypto_tea 2005-03-20 12:11:36.000000000 +0100
+++ kj-domen/crypto/tea.c 2005-03-20 12:11:36.000000000 +0100
@@ -31,8 +31,8 @@
#define XTEA_ROUNDS 32
#define XTEA_DELTA 0x9e3779b9
-#define u32_in(x) le32_to_cpu(*(const u32 *)(x))
-#define u32_out(to, from) (*(u32 *)(to) = cpu_to_le32(from))
+#define u32_in(x) le32_to_cpup((const __le32 *)(x))
+#define u32_out(to, from) (*(__le32 *)(to) = cpu_to_le32(from))
struct tea_ctx {
u32 KEY[4];
_
prev parent reply other threads:[~2005-03-20 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 13:18 [patch 4/4] crypto/tea.c: fix sparse warnings domen
2005-03-20 11:21 ` Domen Puncer [this message]
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=20050320112117.GK14273@nd47.coderock.org \
--to=domen@coderock.org \
--cc=adobriyan@mail.ru \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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