All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave.Martin@arm.com (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v3 0/4] Simplify kernel-mode NEON
Date: Tue, 30 May 2017 19:02:21 +0100	[thread overview]
Message-ID: <20170530180219.GR3559@e103592.cambridge.arm.com> (raw)
In-Reply-To: <1495736721-20985-1-git-send-email-Dave.Martin@arm.com>

On Thu, May 25, 2017 at 07:24:57PM +0100, Dave Martin wrote:
> This series aims to simplify kernel-mode NEON.

Hi Ard, do you have any further comments on this series?

I'd like to have it finalised as far as possible (modulo minor tweaks
and bugfixes) so that I can port the SVE patches on top of it.

Also, how do you think we should handle merging of this change?  There's
a flag-day issue here, since the kernel_mode_neon() API is being changed
in an incompatible way.

Cheers
---Dave

[...]

  parent reply	other threads:[~2017-05-30 18:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 18:24 [RFC PATCH v3 0/4] Simplify kernel-mode NEON Dave Martin
2017-05-25 18:24 ` [RFC PATCH v3 1/4] arm64: neon: Add missing header guard in <asm/neon.h> Dave Martin
2017-05-31 11:41   ` Ard Biesheuvel
2017-05-25 18:24 ` [RFC PATCH v3 2/4] arm64: fpsimd: Consistently use __this_cpu_ ops where appropriate Dave Martin
2017-05-31 11:43   ` Ard Biesheuvel
2017-05-25 18:25 ` [RFC PATCH v3 3/4] arm64: neon: Remove support for nested or hardirq kernel-mode NEON Dave Martin
2017-05-31 11:51   ` Ard Biesheuvel
2017-05-25 18:25 ` [RFC PATCH v3 4/4] arm64: neon: Add backwards compatibility kernel_neon_begin_partial() Dave Martin
2017-05-30 18:02 ` Dave Martin [this message]
2017-05-31  8:41   ` [RFC PATCH v3 0/4] Simplify kernel-mode NEON Ard Biesheuvel
2017-05-31 10:08     ` Dave Martin
2017-05-31 11:07       ` Ard Biesheuvel
2017-05-31 11:33         ` Dave Martin

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=20170530180219.GR3559@e103592.cambridge.arm.com \
    --to=dave.martin@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.