All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dave Martin <Dave.Martin@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/sve: Make fpsimd_bind_task_to_cpu() static
Date: Mon, 2 Aug 2021 17:12:01 +0100	[thread overview]
Message-ID: <20210802161201.GI4668@sirena.org.uk> (raw)
In-Reply-To: <20210802155238.GD25258@arm.com>


[-- Attachment #1.1: Type: text/plain, Size: 656 bytes --]

On Mon, Aug 02, 2021 at 04:52:38PM +0100, Dave Martin wrote:

> Rather makes me wonder
> why it wasn't static in the first place.  This might have arisen from
> splitting out a backend function from something else that isn't static,
> or maybe I was trying to do this directy from KVM.  The notion of non-
> task context that the KVM now uses is newer than the original SVE code.

IIRC there was something like that in the older KVM SVE stuff but I
didn't go spelunking enough to figure it out specifically.

> Anyway, assuming you've grepped and tried to build with KVM at least
> (so, defconfig):

grepped and my standard development builds include KVM.

[-- 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

  reply	other threads:[~2021-08-02 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 16:58 [PATCH] arm64/sve: Make fpsimd_bind_task_to_cpu() static Mark Brown
2021-08-02 15:52 ` Dave Martin
2021-08-02 16:12   ` Mark Brown [this message]
2021-08-02 16:16     ` Dave Martin
2021-08-02 18:06 ` Catalin Marinas

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=20210802161201.GI4668@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Dave.Martin@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@kernel.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.