linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	Will Deacon <will@kernel.org>,
	alexandru.elisei@arm.com, linux-kernel@vger.kernel.org,
	maz@kernel.org
Subject: Re: [PATCH v2 0/5] arm64: irqchip/gic-v3: Use compiletime constant PMR values
Date: Mon, 24 Jun 2024 19:22:22 +0100	[thread overview]
Message-ID: <Znm5XlOSwPqSyTNZ@arm.com> (raw)
In-Reply-To: <87h6dkzmwh.ffs@tglx>

On Sat, Jun 22, 2024 at 11:29:50PM +0200, Thomas Gleixner wrote:
> On Fri, Jun 21 2024 at 18:26, Catalin Marinas wrote:
> > On Mon, Jun 17, 2024 at 12:18:36PM +0100, Mark Rutland wrote:
> >> Mark Rutland (5):
> >>   wordpart.h: Add REPEAT_BYTE_U32()
> >>   irqchip/gic-common: Remove sync_access callback
> >>   irqchip/gic-v3: Make distributor priorities variables
> >>   irqchip/gic-v3: Detect GICD_CTRL.DS and SCR_EL3.FIQ earlier
> >>   arm64: irqchip/gic-v3: Select priorities at boot time
> >> 
> >>  arch/arm64/include/asm/arch_gicv3.h     |  15 --
> >>  arch/arm64/include/asm/ptrace.h         |  35 +---
> >>  arch/arm64/kernel/image-vars.h          |   5 -
> >>  drivers/irqchip/irq-gic-common.c        |  22 +--
> >>  drivers/irqchip/irq-gic-common.h        |   7 +-
> >>  drivers/irqchip/irq-gic-v3-its.c        |  11 +-
> >>  drivers/irqchip/irq-gic-v3.c            | 225 ++++++++++++------------
> >>  drivers/irqchip/irq-gic.c               |  10 +-
> >>  drivers/irqchip/irq-hip04.c             |   6 +-
> >>  include/linux/irqchip/arm-gic-common.h  |   4 -
> >>  include/linux/irqchip/arm-gic-v3-prio.h |  52 ++++++
> >>  include/linux/irqchip/arm-gic-v3.h      |   2 +-
> >>  include/linux/wordpart.h                |   8 +
> >>  13 files changed, 201 insertions(+), 201 deletions(-)
> >>  create mode 100644 include/linux/irqchip/arm-gic-v3-prio.h
> >
> > Are you ok for these patches to go through the arm64 tree (I can put
> > them on a stable branch) or you'd rather get them through the irqchip
> > tree? Either way, I don't expect (major) conflicts with the arm64 tree.
> 
> Take them through your tree with my Acked-by. Yes a branch would be
> appreciated just in case.

Thanks. I added them to the arm64 for-next/gic-v3-pmr branch (on
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git).

> There is also
> 
>       https://lore.kernel.org/all/20240529133446.28446-1-Jonathan.Cameron@huawei.com
> 
> which fiddles with the GIC but most of this is not irqchip code. No idea
> how that is supposed to find it's way into the tree.

I tried to avoid this series so far ;). I'll poke James Morse tomorrow
to see whether he has any outstanding comments (since he started the
work initially). If not, I'll queue them through the arm64 tree (same as
above, on a stable branch in case of conflicts).

Thanks.

-- 
Catalin


  reply	other threads:[~2024-06-24 18:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 11:18 [PATCH v2 0/5] arm64: irqchip/gic-v3: Use compiletime constant PMR values Mark Rutland
2024-06-17 11:18 ` [PATCH v2 1/5] wordpart.h: Add REPEAT_BYTE_U32() Mark Rutland
2024-06-17 11:18 ` [PATCH v2 2/5] irqchip/gic-common: Remove sync_access callback Mark Rutland
2024-06-21  2:22   ` Jinjie Ruan
2024-06-21 11:17     ` Mark Rutland
2024-06-17 11:18 ` [PATCH v2 3/5] irqchip/gic-v3: Make distributor priorities variables Mark Rutland
2024-06-17 11:18 ` [PATCH v2 4/5] irqchip/gic-v3: Detect GICD_CTRL.DS and SCR_EL3.FIQ earlier Mark Rutland
2024-06-17 11:18 ` [PATCH v2 5/5] arm64: irqchip/gic-v3: Select priorities at boot time Mark Rutland
2024-06-21  6:23   ` Liao, Chang
2024-06-21  7:48     ` Marc Zyngier
2024-06-21  8:14       ` Liao, Chang
2024-06-21 17:26 ` [PATCH v2 0/5] arm64: irqchip/gic-v3: Use compiletime constant PMR values Catalin Marinas
2024-06-22 21:29   ` Thomas Gleixner
2024-06-24 18:22     ` Catalin Marinas [this message]
2024-06-24 18:12 ` 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=Znm5XlOSwPqSyTNZ@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=alexandru.elisei@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    --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).