From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] arm64: insn: Add constants for PAC and BTI instruction decode
Date: Tue, 28 Apr 2020 14:33:19 +0100 [thread overview]
Message-ID: <20200428133318.GH6791@willie-the-truck> (raw)
In-Reply-To: <20200428114353.GG5677@sirena.org.uk>
On Tue, Apr 28, 2020 at 12:43:53PM +0100, Mark Brown wrote:
> On Tue, Mar 24, 2020 at 07:48:21PM +0000, Mark Brown wrote:
>
> > + AARCH64_INSN_HINT_BTI = 0x40 << 5,
> > + AARCH64_INSN_HINT_BTIC = 0x42 << 5,
> > + AARCH64_INSN_HINT_BTIJ = 0x44 << 5,
> > + AARCH64_INSN_HINT_BTIJC = 0x4C << 5,
>
> These constants are wrong (I checked the others, they're fine) - I'll
> send out a fixed version as part of the next version of the BTI kernel
> patches since they will depend on these.
Ok, I'll ignore this series then.
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:[~2020-04-28 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 19:48 [PATCH 0/3] arm64: Make NOP handling a whitelist Mark Brown
2020-03-24 19:48 ` [PATCH 1/3] arm64: insn: Don't assume unrecognized HINTs are NOPs Mark Brown
2020-03-24 19:48 ` [PATCH 2/3] arm64: insn: Add constants for PAC and BTI instruction decode Mark Brown
2020-04-28 11:43 ` Mark Brown
2020-04-28 13:33 ` Will Deacon [this message]
2020-03-24 19:48 ` [PATCH 3/3] arm64: insn: Report PAC and BTI instructions as NOPs Mark Brown
2020-04-22 17:27 ` [PATCH 0/3] arm64: Make NOP handling a whitelist 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=20200428133318.GH6791@willie-the-truck \
--to=will@kernel.org \
--cc=amit.kachhap@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@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