[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKv+Gu9o7k0jrrc0jHYUbcJ2k+pmo4N-PHYEZrr_vj=nx-3Z+g@mail.gmail.com>
Date: Fri, 9 Feb 2018 19:28:23 +0000
From: Ard Biesheuvel <ard.biesheuvel@...aro.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dave Martin <Dave.Martin@....com>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Mark Rutland <mark.rutland@....com>,
linux-rt-users@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v4 00/20] crypto: arm64 - play nice with CONFIG_PREEMPT
On 9 February 2018 at 18:02, Sebastian Andrzej Siewior
<bigeasy@...utronix.de> wrote:
> On 2017-12-26 10:29:20 [+0000], Ard Biesheuvel wrote:
>> As reported by Sebastian, the way the arm64 NEON crypto code currently
>> keeps kernel mode NEON enabled across calls into skcipher_walk_xxx() is
> …
>> So let's clean this up for arm64: update the NEON based skcipher drivers to
>> no longer keep the NEON enabled when calling into the skcipher walk API.
>
> Thanks for working on this.
> What is the status of this? Is this going to be merged?
>
Without anybody acking or reviewing it, this is not going to be
merged, so I kind of gave up.
Powered by blists - more mailing lists