[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87tu7skp7w.wl-maz@kernel.org>
Date: Fri, 08 Jul 2022 09:01:23 +0100
From: Marc Zyngier <maz@...nel.org>
To: Frank Li <Frank.Li@....com>
Cc: tglx@...utronix.de, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, shawnguo@...nel.org,
s.hauer@...gutronix.de, kw@...ux.com, bhelgaas@...gle.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-pci@...r.kernel.org,
peng.fan@....com, aisheng.dong@....com, jdmason@...zu.us,
kernel@...gutronix.de, festevam@...il.com, linux-imx@....com,
kishon@...com, lorenzo.pieralisi@....com, ntb@...ts.linux.dev
Subject: Re: [PATCH 1/3] irqchip: imx mu worked as msi controller
On Thu, 07 Jul 2022 22:02:36 +0100,
Frank Li <Frank.Li@....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@....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.
Powered by blists - more mailing lists