From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
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 14:49:30 +0000 [thread overview]
Message-ID: <YbyjerZen9CwYKSV@sirena.org.uk> (raw)
In-Reply-To: <YbyX+I2PBwio0MYk@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
On Fri, Dec 17, 2021 at 02:00:24PM +0000, Catalin Marinas wrote:
> On Thu, Dec 16, 2021 at 09:30:44AM +0530, Naresh Kamboju wrote:
> > [ Please ignore this email if it is already reported ]
It's probably not worth reporting -next issues to the -next maintainer
unless they're specifically in the -next merge - I'd not read this
report since it was part of a small batch of reports you'd sent at the
same time which appeared to be being sent to me because I was running
-next rather than them being directed at me. It can result in things
that need attention getting missed.
> We defined the bti macro in assembler.h but that's not included by
> linkage.h and not all asm files seem to include the former. At a quick
> grep we need the diff below, not sure it's the best solution:
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-17 14:49 UTC|newest]
Thread overview: 6+ 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-17 14:00 ` Catalin Marinas
2021-12-17 14:49 ` Mark Brown [this message]
2021-12-17 15:53 ` Catalin Marinas
2021-12-17 16:12 ` Mark Brown
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=YbyjerZen9CwYKSV@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).