From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [next] arm64: efi-rt-wrapper.S:8: Error: unknown mnemonic `bti' -- `bti c'
Date: Fri, 17 Dec 2021 16:18:17 +0000 [thread overview]
Message-ID: <Yby4SWI97Qb7D43R@arm.com> (raw)
In-Reply-To: <Yby20BrmNBtb6tIq@sirena.org.uk>
On Fri, Dec 17, 2021 at 04:12:00PM +0000, Mark Brown wrote:
> On Fri, Dec 17, 2021 at 03:53:13PM +0000, Catalin Marinas wrote:
> > On Fri, Dec 17, 2021 at 02:49:30PM +0000, Mark Brown wrote:
>
> > > That seems sensible to me, especially given the small number of files
> > > affected. The other thing would be to decide that all assembly files
> > > should have the header included by default but that seems like it's
> > > invasive and probably disproportionate.
>
> > There's also this:
>
> True, that's even simpler.
I'll fold this into your bti patch.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [next] arm64: efi-rt-wrapper.S:8: Error: unknown mnemonic `bti' -- `bti c'
Date: Fri, 17 Dec 2021 16:18:17 +0000 [thread overview]
Message-ID: <Yby4SWI97Qb7D43R@arm.com> (raw)
In-Reply-To: <Yby20BrmNBtb6tIq@sirena.org.uk>
On Fri, Dec 17, 2021 at 04:12:00PM +0000, Mark Brown wrote:
> On Fri, Dec 17, 2021 at 03:53:13PM +0000, Catalin Marinas wrote:
> > On Fri, Dec 17, 2021 at 02:49:30PM +0000, Mark Brown wrote:
>
> > > That seems sensible to me, especially given the small number of files
> > > affected. The other thing would be to decide that all assembly files
> > > should have the header included by default but that seems like it's
> > > invasive and probably disproportionate.
>
> > There's also this:
>
> True, that's even simpler.
I'll fold this into your bti patch.
--
Catalin
_______________________________________________
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-12-17 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 4:00 [next] arm64: efi-rt-wrapper.S:8: Error: unknown mnemonic `bti' -- `bti c' Naresh Kamboju
2021-12-16 4:00 ` Naresh Kamboju
2021-12-17 14:00 ` Catalin Marinas
2021-12-17 14:00 ` Catalin Marinas
2021-12-17 14:49 ` Mark Brown
2021-12-17 14:49 ` Mark Brown
2021-12-17 15:53 ` Catalin Marinas
2021-12-17 15:53 ` Catalin Marinas
2021-12-17 16:12 ` Mark Brown
2021-12-17 16:12 ` Mark Brown
2021-12-17 16:18 ` Catalin Marinas [this message]
2021-12-17 16:18 ` 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=Yby4SWI97Qb7D43R@arm.com \
--to=catalin.marinas@arm.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=sfr@canb.auug.org.au \
--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.