devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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.

  parent reply	other threads:[~2022-07-08  8:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 21:02 [PATCH 1/3] irqchip: imx mu worked as msi controller Frank Li
2022-07-07 21:02 ` [PATCH 2/3] dt-bindings: irqchip: imx mu work " Frank Li
2022-07-08 21:32   ` Rob Herring
2022-07-12 10:25   ` Krzysztof Kozlowski
2022-07-15 19:35     ` [EXT] " Frank Li
2022-07-07 21:02 ` [PATCH 3/3] pcie: endpoint: pci-epf-vntb: add endpoint msi support Frank Li
2022-07-08  8:01 ` Marc Zyngier [this message]
2022-07-08  8:58 ` [PATCH 1/3] irqchip: imx mu worked as msi controller Marc Zyngier
2022-07-08 16:26   ` [EXT] " Frank Li
2022-07-09  8:16     ` Marc Zyngier
2022-07-09 15:23       ` Frank Li
2022-07-13 18:28         ` Frank Li

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=87tu7skp7w.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=jdmason@kudzu.us \
    --cc=kernel@pengutronix.de \
    --cc=kishon@ti.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=ntb@lists.linux.dev \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).