All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Radu Rendec <radu@rendec.net>, Guo Ren <guoren@kernel.org>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Daniel Lezcano <daniel.lezcano@kernel.org>,
	Anup Patel <anup@brainfault.org>,
	Tiffany Lin <tiffany.lin@mediatek.com>,
	Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
	Yunfei Dong <yunfei.dong@mediatek.com>,
	Minghsiu Tsai <minghsiu.tsai@mediatek.com>,
	Houlong Wei <houlong.wei@mediatek.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	"tip-bot2 for GUO Ren (XuanTie)" <tip-bot2@linutronix.de>,
	Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v2 0/6] riscv: Make IPI_MAX visible and use it consistently
Date: Thu, 15 Oct 2026 14:35:35 +0200	[thread overview]
Message-ID: <87o6cvdtuw.ffs@fw13> (raw)
In-Reply-To: <6a4202752078c5f55882d3a4f5113829201dfb7b.camel@rendec.net>

On Thu, Sep 17 2026 at 21:38, Radu Rendec wrote:
> I now realize that patch 1 (which introduces the conflicting change)
> was picked up by Thomas via the irq/drivers tip branch, but patch 6 is
> strictly a media subsystem patch, so I guess normally it should be
> picked up by a different maintainer via a different tree.
>
> Thomas, are you willing to pick this up too? I'm thinking it could
> avoid some pain if irq/drivers gets merged into mainline first, before
> patch 6 makes it there through the media subsystem. Also, it's a pretty
> "innocent" patch, it just renames an enum value, and it's contained
> within that driver.

The media folks picked it up already.


WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@kernel.org>
To: Radu Rendec <radu@rendec.net>, Guo Ren <guoren@kernel.org>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Daniel Lezcano <daniel.lezcano@kernel.org>,
	Anup Patel <anup@brainfault.org>,
	Tiffany Lin <tiffany.lin@mediatek.com>,
	Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
	Yunfei Dong <yunfei.dong@mediatek.com>,
	Minghsiu Tsai <minghsiu.tsai@mediatek.com>,
	Houlong Wei <houlong.wei@mediatek.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	"tip-bot2 for GUO Ren (XuanTie)" <tip-bot2@linutronix.de>,
	Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v2 0/6] riscv: Make IPI_MAX visible and use it consistently
Date: Thu, 15 Oct 2026 14:35:35 +0200	[thread overview]
Message-ID: <87o6cvdtuw.ffs@fw13> (raw)
In-Reply-To: <6a4202752078c5f55882d3a4f5113829201dfb7b.camel@rendec.net>

On Thu, Sep 17 2026 at 21:38, Radu Rendec wrote:
> I now realize that patch 1 (which introduces the conflicting change)
> was picked up by Thomas via the irq/drivers tip branch, but patch 6 is
> strictly a media subsystem patch, so I guess normally it should be
> picked up by a different maintainer via a different tree.
>
> Thomas, are you willing to pick this up too? I'm thinking it could
> avoid some pain if irq/drivers gets merged into mainline first, before
> patch 6 makes it there through the media subsystem. Also, it's a pretty
> "innocent" patch, it just renames an enum value, and it's contained
> within that driver.

The media folks picked it up already.

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-10-15 12:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  3:27 [PATCH v2 0/6] riscv: Make IPI_MAX visible and use it consistently Guo Ren
2026-09-11  3:27 ` Guo Ren
2026-09-11  3:27 ` [PATCH v2 1/6] riscv: smp: Move enum ipi_message_type to asm/smp.h Guo Ren
2026-09-11  3:27   ` Guo Ren
2026-09-11  3:27 ` [PATCH v2 2/6] riscv: sbi: Use IPI_MAX for SBI IPI muxing Guo Ren
2026-09-11  3:27   ` Guo Ren
2026-09-11  3:27 ` [PATCH v2 3/6] clocksource: clint: Use IPI_MAX for " GUO Ren (XuanTie)
2026-09-11  3:27   ` GUO Ren (XuanTie)
2026-10-02  9:52   ` Daniel Lezcano
2026-10-02  9:52     ` Daniel Lezcano
2026-09-11  3:27 ` [PATCH v2 4/6] irqchip/aclint-sswi: " GUO Ren (XuanTie)
2026-09-11  3:27   ` GUO Ren (XuanTie)
2026-09-11  3:27 ` [PATCH v2 5/6] irqchip/imsic: Use IPI_MAX instead of IMSIC_NR_IPI GUO Ren (XuanTie)
2026-09-11  3:27   ` GUO Ren (XuanTie)
2026-09-11  3:27 ` [PATCH v2 6/6] media: mtk-vpu: rename IPI_MAX to IPI_VPU_MAX GUO Ren (XuanTie)
2026-09-11  3:27   ` GUO Ren (XuanTie)
2026-09-18  1:21   ` Radu Rendec
2026-09-18  1:21     ` Radu Rendec
2026-10-04 11:03     ` Nicolas Dufresne
2026-10-04 11:03       ` Nicolas Dufresne
2026-09-13 19:53 ` [PATCH v2 0/6] riscv: Make IPI_MAX visible and use it consistently Radu Rendec
2026-09-13 19:53   ` Radu Rendec
2026-09-17 11:22   ` Guo Ren
2026-09-17 11:22     ` Guo Ren
2026-09-18  1:38     ` Radu Rendec
2026-09-18  1:38       ` Radu Rendec
2026-10-15 12:35       ` Thomas Gleixner [this message]
2026-10-15 12:35         ` Thomas Gleixner

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=87o6cvdtuw.ffs@fw13 \
    --to=tglx@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=andrew-ct.chen@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=daniel.lezcano@kernel.org \
    --cc=guoren@kernel.org \
    --cc=houlong.wei@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=minghsiu.tsai@mediatek.com \
    --cc=nathan@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=radu@rendec.net \
    --cc=tiffany.lin@mediatek.com \
    --cc=tip-bot2@linutronix.de \
    --cc=yunfei.dong@mediatek.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.