On Tue, 19 Feb 2019 at 12:19, Greg KH wrote:
>
> On Tue, Feb 19, 2019 at 11:35:12AM +0100, Ard Biesheuvel wrote:
> > On Fri, 15 Feb 2019 at 20:45, Ard Biesheuvel
> > wrote:
> > >
> > > On Fri, 15 Feb 2019 at 20:43, Nick Desaulniers
> > > wrote:
> > > >
> > > > On Fri, Feb 15, 2019 at 11:28 AM
On Tue, Feb 19, 2019 at 11:35:12AM +0100, Ard Biesheuvel wrote:
> On Fri, 15 Feb 2019 at 20:45, Ard Biesheuvel
> wrote:
> >
> > On Fri, 15 Feb 2019 at 20:43, Nick Desaulniers
> > wrote:
> > >
> > > On Fri, Feb 15, 2019 at 11:28 AM Ard Biesheuvel
> > > wrote:
> > > >
> > > > On Fri, 15 Feb
On Fri, 15 Feb 2019 at 20:45, Ard Biesheuvel wrote:
>
> On Fri, 15 Feb 2019 at 20:43, Nick Desaulniers
> wrote:
> >
> > On Fri, Feb 15, 2019 at 11:28 AM Ard Biesheuvel
> > wrote:
> > >
> > > On Fri, 15 Feb 2019 at 20:25, Nick Desaulniers
> > > wrote:
> > > >
> > > > On Fri, Feb 15, 2019 at
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.
>
> arch/arm64/lib/xor-neon.c:58:28: error: incompatible pointer
On Fri, 15 Feb 2019 at 20:43, Nick Desaulniers wrote:
>
> On Fri, Feb 15, 2019 at 11:28 AM Ard Biesheuvel
> wrote:
> >
> > On Fri, 15 Feb 2019 at 20:25, Nick Desaulniers
> > wrote:
> > >
> > > On Fri, Feb 15, 2019 at 11:20 AM Ard Biesheuvel
> > > wrote:
> > > > Provided that we stop sending
On Fri, Feb 15, 2019 at 11:28 AM Ard Biesheuvel
wrote:
>
> On Fri, 15 Feb 2019 at 20:25, Nick Desaulniers
> wrote:
> >
> > On Fri, Feb 15, 2019 at 11:20 AM Ard Biesheuvel
> > wrote:
> > > Provided that we stop sending Clang enablement patches to -stable:
> >
> > What does that mean? We're
On Fri, 15 Feb 2019 at 20:25, Nick Desaulniers wrote:
>
> On Fri, Feb 15, 2019 at 11:20 AM Ard Biesheuvel
> wrote:
> > Provided that we stop sending Clang enablement patches to -stable:
>
> What does that mean? We're trying to provide clang support back to
> 4.4 LTS branches. (so 4.4, 4.9,
On Fri, Feb 15, 2019 at 11:20 AM Ard Biesheuvel
wrote:
> Provided that we stop sending Clang enablement patches to -stable:
What does that mean? We're trying to provide clang support back to
4.4 LTS branches. (so 4.4, 4.9, 4.14, 4.19).
--
Thanks,
~Nick Desaulniers
On Fri, 15 Feb 2019 at 19:50, Will Deacon wrote:
>
> 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.
> >
>
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
signature.asc
Description: PGP
After commit cc9f8349cb33 ("arm64: crypto: add NEON accelerated XOR
implementation"), Clang builds for arm64 started failing with the
following error message.
arch/arm64/lib/xor-neon.c:58:28: error: incompatible pointer types
assigning to 'const unsigned long *' from 'uint64_t *' (aka 'unsigned
11 matches
Mail list logo