From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephan Mueller <smueller@chronox.de>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DRBG: fix sparse warning for cpu_to_be[32|64]
Date: Tue, 26 Aug 2014 15:34:01 +0800 [thread overview]
Message-ID: <20140826073401.GA3962@gondor.apana.org.au> (raw)
In-Reply-To: <1803846.LZmvEct3qr@myon.chronox.de>
On Tue, Aug 26, 2014 at 09:32:24AM +0200, Stephan Mueller wrote:
> The sparse tool complained that the cpu_to_be[32|64] functions return
> __be[32|64] instead of __u32 or __u64. The patch replaces the __u32 and
> __u64 with __be32 and __be64.
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Stephan Mueller <smueller@chronox.de>
Patch applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2014-08-26 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53fc2da5.AS8xtJ0DprRMVjVq%fengguang.wu@intel.com>
2014-08-26 7:32 ` [PATCH] DRBG: fix sparse warning for cpu_to_be[32|64] Stephan Mueller
2014-08-26 7:34 ` Herbert Xu [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=20140826073401.GA3962@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.de \
/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