From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Marc Zyngier <maz@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH v4] arm64: smccc: Support SMCCC v1.3 SVE register saving hint
Date: Thu, 27 May 2021 09:18:32 +0100 [thread overview]
Message-ID: <20210527081832.GC21235@willie-the-truck> (raw)
In-Reply-To: <20210527080953.GA21235@willie-the-truck>
On Thu, May 27, 2021 at 09:09:53AM +0100, Will Deacon wrote:
> On Thu, May 27, 2021 at 12:02:48AM +0100, Mark Brown wrote:
> > On Wed, May 26, 2021 at 10:31:29PM +0100, Will Deacon wrote:
> > > On Mon, May 24, 2021 at 11:42:53AM +0100, Mark Brown wrote:
> >
> > > > drivers/firmware/smccc/smccc.c | 4 ++++
> > > > include/linux/arm-smccc.h | 24 ++++++++++++++++++++++--
> > > > 3 files changed, 52 insertions(+), 2 deletions(-)
> >
> > > This fails to build for me:
> >
> > Interesting... which toolchain are you using here?
>
> That's a good question.
>
> /me digs into scripts
>
> I think it's:
>
> gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))
Duh, I suppose you're probably more interested in the assembler:
GNU assembler (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-27 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 10:42 [PATCH v4] arm64: smccc: Support SMCCC v1.3 SVE register saving hint Mark Brown
2021-05-26 21:31 ` Will Deacon
2021-05-26 23:02 ` Mark Brown
2021-05-27 8:09 ` Will Deacon
2021-05-27 8:18 ` Will Deacon [this message]
2021-05-31 5:52 ` Ard Biesheuvel
2021-06-01 12:45 ` 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=20210527081832.GC21235@willie-the-truck \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=maz@kernel.org \
--cc=sudeep.holla@arm.com \
/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