From: Mark Brown <broonie@kernel.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/neon: Disable -Wincompatible-pointer-types when building with Clang
Date: Fri, 15 Feb 2019 11:50:01 +0000 [thread overview]
Message-ID: <20190215115001.GA7897@sirena.org.uk> (raw)
In-Reply-To: <20190215013959.21320-1-natechancellor@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 278 bytes --]
On Thu, Feb 14, 2019 at 06:39:59PM -0700, Nathan Chancellor wrote:
> After commit cc9f8349cb33 ("arm64: crypto: add NEON accelerated XOR
> implementation"), Clang builds for arm64 started failing with the
> following error message.
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-15 11:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 1:39 [PATCH] arm64/neon: Disable -Wincompatible-pointer-types when building with Clang Nathan Chancellor
2019-02-15 11:50 ` Mark Brown [this message]
2019-02-15 18:50 ` Will Deacon
2019-02-15 19:20 ` Ard Biesheuvel
2019-02-15 19:25 ` Nick Desaulniers
2019-02-15 19:28 ` Ard Biesheuvel
2019-02-15 19:43 ` Nick Desaulniers
2019-02-15 19:45 ` Ard Biesheuvel
2019-02-19 10:35 ` Ard Biesheuvel
2019-02-19 11:19 ` Greg KH
2019-02-19 11:35 ` Ard Biesheuvel
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=20190215115001.GA7897@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=will.deacon@arm.com \
/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).