Re: [PATCH 1/3] irqchip: imx mu worked as msi controller

From: Marc Zyngier <maz@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: tglx@linutronix.de, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, kw@linux.com, bhelgaas@google.com,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
	peng.fan@nxp.com, aisheng.dong@nxp.com, jdmason@kudzu.us,
	kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	kishon@ti.com, lorenzo.pieralisi@arm.com, ntb@lists.linux.dev
Subject: Re: [PATCH 1/3] irqchip: imx mu worked as msi controller
Date: Fri, 08 Jul 2022 09:01:23 +0100	[thread overview]
Message-ID: <87tu7skp7w.wl-maz@kernel.org> (raw)
In-Reply-To: <20220707210238.917477-1-Frank.Li@nxp.com>

On Thu, 07 Jul 2022 22:02:36 +0100,
Frank Li <Frank.Li@nxp.com> wrote:
> 
> MU support generate irq by write data to a register.
> This patch make mu worked as msi controller.
> So MU can do doorbell by using standard msi api.
> 
> Signed-off-by: Frank Li <Frank.Li@nxp.com>

Where is the cover letter for this? How am I supposed to guess what
this series is about? The rule is simple: you send a series with two
patches or more, you include a cover letter describing your changes,
what they provide, and how they interact with each other. Here, all I
see is a bunch of seemingly unrelated changes.

I could spend the next 2 hours trying to reverse engineer it, but it
is probably a lot quicker for you to write an actual cover letter and
send it for everyone's benefit.

Thanks,

	M.

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