From: Arnd Bergmann <arnd@arndb.de>
To: linaro-kernel@lists.linaro.org
Cc: "Build bot for Mark Brown" <broonie@kernel.org>,
kernel-build-reports@lists.linaro.org,
"Horia Geantă" <horia.geanta@nxp.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org
Subject: crypto: caam warning fix, was: master build: 0 failures 1 warnings (v4.9-rc5-177-g81bcfe5)
Date: Wed, 16 Nov 2016 17:40:41 +0100 [thread overview]
Message-ID: <5255539.MpGQJX1bep@wuerfel> (raw)
In-Reply-To: <E1c6kSQ-0008UC-DM@optimist>
On Tuesday, November 15, 2016 8:35:54 PM CET Build bot for Mark Brown wrote:
> Tree/Branch: master
> Git describe: v4.9-rc5-177-g81bcfe5
> Commit: 81bcfe5e48 Merge tag 'trace-v4.9-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
>
> Build Time: 87 min 40 sec
>
> Passed: 10 / 10 (100.00 %)
> Failed: 0 / 10 ( 0.00 %)
>
> Errors: 0
> Warnings: 1
> Section Mismatches: 0
>
> -------------------------------------------------------------------------------
> defconfigs with issues (other than build errors):
> 1 warnings 0 mismatches : arm64-allmodconfig
>
> -------------------------------------------------------------------------------
>
> Warnings Summary: 1
> 1 ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast
>
Hi Herbert,
This is currently the only build warning reported for v4.9, and you have merged
the fix for v4.10 in
d69985a07692 ("crypto: caam - fix type mismatch warning")
Any chance you can send this for v4.9 so we have a clean build?
Thanks,
Arnd
next parent reply other threads:[~2016-11-16 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1c6kSQ-0008UC-DM@optimist>
2016-11-16 16:40 ` Arnd Bergmann [this message]
2016-11-17 15:34 ` crypto: caam warning fix, was: master build: 0 failures 1 warnings (v4.9-rc5-177-g81bcfe5) Herbert Xu
2016-11-17 15:42 ` Arnd Bergmann
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=5255539.MpGQJX1bep@wuerfel \
--to=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--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