From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Shanker Donthineni <shankerd@codeaurora.org>,
Vikram Sethi <vikrams@codeaurora.org>,
Sean Campbell <scampbel@codeaurora.org>,
Marc Zyngier <marc.zyngier@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Christoffer Dall <christoffer.dall@linaro.org>,
kvmarm <kvmarm@lists.cs.columbia.edu>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: Implement branch predictor hardening for Falkor
Date: Tue, 9 Jan 2018 11:05:47 +0000 [thread overview]
Message-ID: <20180109110547.ok35kw5e4rwicnf3@localhost> (raw)
In-Reply-To: <20180109094146.GB4297@arm.com>
On Tue, Jan 09, 2018 at 09:41:46AM +0000, Will Deacon wrote:
> You'll need to send a fixup patch. for-next/core is non-rebasing.
I haven't pushed it out yet (will do this morning) but note that
for-next/core is based on 4.15-rc3.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Implement branch predictor hardening for Falkor
Date: Tue, 9 Jan 2018 11:05:47 +0000 [thread overview]
Message-ID: <20180109110547.ok35kw5e4rwicnf3@localhost> (raw)
In-Reply-To: <20180109094146.GB4297@arm.com>
On Tue, Jan 09, 2018 at 09:41:46AM +0000, Will Deacon wrote:
> You'll need to send a fixup patch. for-next/core is non-rebasing.
I haven't pushed it out yet (will do this morning) but note that
for-next/core is based on 4.15-rc3.
--
Catalin
next prev parent reply other threads:[~2018-01-09 11:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 20:28 [PATCH] arm64: Implement branch predictor hardening for Falkor Shanker Donthineni
2018-01-05 20:28 ` Shanker Donthineni
2018-01-08 9:28 ` Andrew Jones
2018-01-08 9:28 ` Andrew Jones
2018-01-08 17:22 ` Shanker Donthineni
2018-01-08 17:22 ` Shanker Donthineni
2018-01-08 17:22 ` Shanker Donthineni
2018-01-08 17:09 ` Will Deacon
2018-01-08 17:09 ` Will Deacon
2018-01-08 18:44 ` Will Deacon
2018-01-08 18:44 ` Will Deacon
2018-01-08 18:44 ` Will Deacon
2018-01-08 19:10 ` Shanker Donthineni
2018-01-08 19:10 ` Shanker Donthineni
2018-01-08 21:44 ` Shanker Donthineni
2018-01-08 21:44 ` Shanker Donthineni
2018-01-08 21:44 ` Shanker Donthineni
2018-01-09 9:41 ` Will Deacon
2018-01-09 9:41 ` Will Deacon
2018-01-09 9:41 ` Will Deacon
2018-01-09 11:05 ` Catalin Marinas [this message]
2018-01-09 11:05 ` 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=20180109110547.ok35kw5e4rwicnf3@localhost \
--to=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=scampbel@codeaurora.org \
--cc=shankerd@codeaurora.org \
--cc=vikrams@codeaurora.org \
--cc=will.deacon@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 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.