All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Breno Leitao <leitao@debian.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh@kernel.org>,
	Sascha Bischoff <sascha.bischoff@arm.com>,
	Timothy Hayes <timothy.hayes@arm.com>,
	Will Deacon <will@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev
Subject: Re: [GIT PULL] irqchip: Add GICv5 support
Date: Sat, 19 Jul 2025 08:32:43 +0100	[thread overview]
Message-ID: <86seis8wkk.wl-maz@kernel.org> (raw)
In-Reply-To: <87y0slur4t.ffs@tglx>

On Fri, 18 Jul 2025 22:26:58 +0100,
Thomas Gleixner <tglx@linutronix.de> wrote:
> 
> Marc!
> 
> On Thu, Jul 17 2025 at 13:23, Marc Zyngier wrote:
> 
> > Thomas,
> >
> > After some time simmering in -next without much catching fire (only a
> > single regression has been reported, which was promptly fixed), here's
> > the pull request for the GICv5 core infrastructure.
> >
> > There are still a couple of patches on the list (mostly addressing
> > error paths, and actively being reviewed), but I don't see anything
> > that would warrant holding this any longer, and these fixes can be
> > added down the line. If anything, this work has allowed us to
> > pipe-clean a number of issues in the tree.
> >
> > Please note that the kvmarm tree also carries this branch, as this is
> > a dependency for enabling GICv3 compatibility for guests on a GICv5
> > host.
> 
> I'm fine with keeping this in the kvmarm tree only if that is intended
> to hit the next merge window. There is no point to carry this
> redundantly in two trees, unless there is some conflict to resolve in my
> tree.

Thanks for that, I'll keep the branch around anyway, should you need
to pull it to resolve some last minute conflict.

> If the kvmarm stuff is not ready yet, then please let me know and I
> happily pull in the pile.

The kvmarm stuff is ready to go, has been simmering in -next for the
same time, and is also aiming for 6.17.

Thanks again,

	M.

-- 
Without deviation from the norm, progress is not possible.

      reply	other threads:[~2025-07-19  7:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17 12:23 [GIT PULL] irqchip: Add GICv5 support Marc Zyngier
2025-07-18 21:26 ` Thomas Gleixner
2025-07-19  7:32   ` Marc Zyngier [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=86seis8wkk.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=leitao@debian.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=oliver.upton@linux.dev \
    --cc=robh@kernel.org \
    --cc=sascha.bischoff@arm.com \
    --cc=tglx@linutronix.de \
    --cc=timothy.hayes@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 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.