From: Mark Brown <broonie@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: kvm: Modernize annotation for __bp_harden_hyp_vecs
Date: Tue, 18 Feb 2020 13:29:46 +0000 [thread overview]
Message-ID: <20200218132946.GF4232@sirena.org.uk> (raw)
In-Reply-To: <20200218130953.GD20212@willie-the-truck>
[-- Attachment #1.1: Type: text/plain, Size: 975 bytes --]
On Tue, Feb 18, 2020 at 01:09:53PM +0000, Will Deacon wrote:
> On Tue, Feb 18, 2020 at 12:56:52PM +0000, Marc Zyngier wrote:
> > I'd really appreciate it if you could send these as a series, instead of
> > an isolated patch every other day.
> Same for the non-KVM parts, please :)
Ugh, right. As one series or as different serieses for the different
trees that apply things (eg, KVM and crypto)? The multi tree stuff
worries me.
> I *think* the current ones to track are:
Yes, apart from:
> [PATCH v6 00/11] arm64: Branch Target Identification support
The BTI stuff is unrelated at this point, the annotations are only
needed for in kernel BTI which I've not posted yet, it also depends on
the in kernel pointer authentication stuff so I was waiting for that to
settle down before I finish off the in kernel bits and post them.
Pulling it into the series with the asm stuff would result in a very big
series with an absurdly large CC list which doesn't seem helpful.
[-- 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
next prev parent reply other threads:[~2020-02-18 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 12:44 [PATCH] arm64: kvm: Modernize annotation for __bp_harden_hyp_vecs Mark Brown
2020-02-18 12:56 ` Marc Zyngier
2020-02-18 13:06 ` Mark Brown
2020-02-18 13:14 ` Will Deacon
2020-02-18 13:45 ` Mark Brown
2020-02-18 13:09 ` Will Deacon
2020-02-18 13:29 ` Mark Brown [this message]
2020-02-18 13:35 ` Marc Zyngier
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=20200218132946.GF4232@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--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).