Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Marc Zyngier <maz@kernel.org>, Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] KVM: arm64: Enable Cortex-A510 erratum 2077057 by default
Date: Tue, 8 Mar 2022 18:44:21 +0000	[thread overview]
Message-ID: <YiekBfx2Dj8xU78/@arm.com> (raw)
In-Reply-To: <YiejnUtIRCu9fMtk@arm.com>

On Tue, Mar 08, 2022 at 06:42:45PM +0000, Catalin Marinas wrote:
> On Fri, Feb 25, 2022 at 06:46:58PM +0000, Mark Brown wrote:
> > The recently added configuration option for Cortex A510 erratum 2077057 does
> > not have a "default y" unlike other errata fixes. This appears to simply be
> > an oversight since the help text suggests enabling the option if unsure and
> > there's nothing in the commit log to suggest it is intentional.
> > 
> > Fixes: 1dd498e5e26ad ("KVM: arm64: Workaround Cortex-A510's single-step and PAC trap errata")
> > Signed-off-by: Mark Brown <broonie@kernel.org>
> 
> I don't think Will picked this up, so:
> 
> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>

Ah, I should call it a day. I already acked this patch and Marc queued
it.

-- 
Catalin
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

      reply	other threads:[~2022-03-08 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 18:46 [PATCH] KVM: arm64: Enable Cortex-A510 erratum 2077057 by default Mark Brown
2022-03-02 14:09 ` Catalin Marinas
2022-03-02 15:01   ` Marc Zyngier
2022-03-02 15:05 ` Marc Zyngier
2022-03-08 18:42 ` Catalin Marinas
2022-03-08 18:44   ` Catalin Marinas [this message]

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=YiekBfx2Dj8xU78/@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=broonie@kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --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