From: "Marek Behún" <kabel@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
soc@kernel.org, linux-arm-kernel@lists.infradead.org,
arm@kernel.org, "Andy Shevchenko" <andy@kernel.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v3 0/5] armada-370-xp irqchip updates
Date: Mon, 1 Jul 2024 19:00:41 +0200 [thread overview]
Message-ID: <20240701190041.286241ec@dellmb> (raw)
In-Reply-To: <20240621093832.23319-1-kabel@kernel.org>
On Fri, 21 Jun 2024 11:38:27 +0200
Marek Behún <kabel@kernel.org> wrote:
> Hi Arnd, Andrew, et al.
>
> this is v3 of updates for armada-370-xp irqchip. There is one small fix,
> and another patch added which was previosly sent separately.
>
> Also I realized that I did not send to the SoC mailing list, nor to
> Arnd.
>
> As written in previous cover letter: this driver is in need of a major
> refactor in order to bring it to modern standards, but that is
> unfortunately currently infeasible with my time constraints.
>
> v1 and v2 at:
> https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=863473
> https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=863707
>
> Changes since v2:
> - dropped redundant assignment during declaration in patch 4
> (bool src0 = false, src1 = false)
> - added patch 5 to this series, previously sent separately
>
> Marek Behún (1):
> irqchip/armada-370-xp: Use atomic_io_modify() instead of another
> spinlock
>
> Pali Rohár (4):
> irqchip/armada-370-xp: Do not allow mapping IRQ 0 and 1
> irqchip/armada-370-xp: Only call ipi_resume() if IPI is available
> irqchip/armada-370-xp: Do not touch IPI registers on platforms without
> IPI
> irqchip/armada-370-xp: Add support for 32 MSI interrupts on non-IPI
> platforms
>
> drivers/irqchip/irq-armada-370-xp.c | 121 ++++++++++++++++++++++------
> 1 file changed, 95 insertions(+), 26 deletions(-)
>
Hi Arnd,
just noting that these changes were also accepted, by Thomas Glexiner.
No need to apply to soc. (I marked them as Awainting Upstream on
patchwork).
Marek
prev parent reply other threads:[~2024-07-01 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 9:38 [PATCH v3 0/5] armada-370-xp irqchip updates Marek Behún
2024-06-21 9:38 ` [PATCH v3 1/5] irqchip/armada-370-xp: Do not allow mapping IRQ 0 and 1 Marek Behún
2024-06-21 9:38 ` [PATCH v3 2/5] irqchip/armada-370-xp: Only call ipi_resume() if IPI is available Marek Behún
2024-06-21 9:38 ` [PATCH v3 3/5] irqchip/armada-370-xp: Do not touch IPI registers on platforms without IPI Marek Behún
2024-06-21 9:38 ` [PATCH v3 4/5] irqchip/armada-370-xp: Add support for 32 MSI interrupts on non-IPI platforms Marek Behún
2024-06-21 9:38 ` [PATCH v3 5/5] irqchip/armada-370-xp: Use atomic_io_modify() instead of another spinlock Marek Behún
2024-07-01 17:00 ` Marek Behún [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=20240701190041.286241ec@dellmb \
--to=kabel@kernel.org \
--cc=andrew@lunn.ch \
--cc=andy@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=gregory.clement@bootlin.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=soc@kernel.org \
--cc=tglx@linutronix.de \
/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