Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/fpsimd: Add interface for kernel use of SVE and SME
Date: Mon, 7 Nov 2022 13:03:55 +0000	[thread overview]
Message-ID: <20221107130354.GA19956@willie-the-truck> (raw)
In-Reply-To: <Y2Zr/3LPrlmQSs7t@sirena.org.uk>

On Sat, Nov 05, 2022 at 01:58:23PM +0000, Mark Brown wrote:
> On Sat, Nov 05, 2022 at 01:29:34AM -0700, Christoph Hellwig wrote:
> > On Thu, Nov 03, 2022 at 06:07:04PM +0000, Mark Brown wrote:
> > > +EXPORT_SYMBOL(kernel_fp_begin);
> 
> > All in-kernel FPU usage needs to be EXPORT_SYMBOL_GPL.
> 
> That'd be a change for arm4, the existing exports for access to
> NEON are plain EXPORT_SYMBOLs.  I'll defer that one to Catalin
> and Will.

I'm happy for everything to use the GPL flavours. I suspect the existing
exports are like they are only because the macro is shorter to type.

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-11-07 13:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 18:07 [PATCH] arm64/fpsimd: Add interface for kernel use of SVE and SME Mark Brown
2022-11-03 18:09 ` Ard Biesheuvel
2022-11-03 18:19   ` Mark Brown
2022-11-05  8:29 ` Christoph Hellwig
2022-11-05 13:58   ` Mark Brown
2022-11-07 13:03     ` Will Deacon [this message]
2022-11-07 14:43       ` Mark Brown

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=20221107130354.GA19956@willie-the-truck \
    --to=will@kernel.org \
    --cc=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=hch@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox