From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Sascha Bischoff <Sascha.Bischoff@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>, nd <nd@arm.com>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
Joey Gouly <Joey.Gouly@arm.com>,
Suzuki Poulose <Suzuki.Poulose@arm.com>,
"yuzenghui@huawei.com" <yuzenghui@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Aishwarya.TCV@arm.com
Subject: Re: [PATCH] KVM: arm64: gic-v3: Only set ICH_HCR traps for v2-on-v3 or v3 guests
Date: Tue, 21 Oct 2025 15:37:59 +0100 [thread overview]
Message-ID: <86bjm0wcag.wl-maz@kernel.org> (raw)
In-Reply-To: <78b0297c-4622-4b75-bcae-45c144c92c45@sirena.org.uk>
On Tue, 21 Oct 2025 15:00:30 +0100,
Mark Brown <broonie@kernel.org> wrote:
>
> On Tue, Oct 21, 2025 at 08:50:22AM +0100, Marc Zyngier wrote:
> > Mark Brown <broonie@kernel.org> wrote:
>
> The only thing I can think of is that you are objecting to the idea of
> having the KVM arm64 tree merge it's fixes branch into it's development
> branch. That is not what I am suggesting, I am suggesting putting the
> fixes branch itself directly into -next to be merged by Stephen. I am
> not proposing any change to the content of the KVM arm64 branches.
Then I don't know why you even involve me here.
You can pull anything you want in -next, and you don't need my
approval for it. I still don't think this is a good idea because the
life cycles are totally different, but if you like making your own
life complicated, go ahead, I'm not going to stop you.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-10-21 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 16:07 [PATCH] KVM: arm64: gic-v3: Only set ICH_HCR traps for v2-on-v3 or v3 guests Sascha Bischoff
2025-10-13 16:56 ` Marc Zyngier
2025-10-21 0:21 ` Mark Brown
2025-10-21 0:50 ` Sean Christopherson
2025-10-21 11:39 ` Mark Brown
2025-10-21 7:50 ` Marc Zyngier
2025-10-21 14:00 ` Mark Brown
2025-10-21 14:37 ` Marc Zyngier [this message]
2025-10-21 18:47 ` Mark Brown
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=86bjm0wcag.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Aishwarya.TCV@arm.com \
--cc=Joey.Gouly@arm.com \
--cc=Sascha.Bischoff@arm.com \
--cc=Suzuki.Poulose@arm.com \
--cc=broonie@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nd@arm.com \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=yuzenghui@huawei.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.