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,
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, lznuaa@gmail.com
Subject: Re: [PATCH v4 2/4] irqchip: imx mu worked as msi controller
Date: Sat, 13 Aug 2022 12:57:25 +0100 [thread overview]
Message-ID: <874jygs6e2.wl-maz@kernel.org> (raw)
In-Reply-To: <20220812215242.2255824-3-Frank.Li@nxp.com>
On Fri, 12 Aug 2022 22:52:40 +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>
May I add that it wouldn't hurt if you checked what addresses you send
your patches to? For example, 'kernel@vger.kernel.org' doesn't exist
(maybe you meant linux-kernel@...).
I will not take patches that haven't been posted to LKML (and I
shouldn't have reviewed it the first place).
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
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,
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, lznuaa@gmail.com
Subject: Re: [PATCH v4 2/4] irqchip: imx mu worked as msi controller
Date: Sat, 13 Aug 2022 12:57:25 +0100 [thread overview]
Message-ID: <874jygs6e2.wl-maz@kernel.org> (raw)
In-Reply-To: <20220812215242.2255824-3-Frank.Li@nxp.com>
On Fri, 12 Aug 2022 22:52:40 +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>
May I add that it wouldn't hurt if you checked what addresses you send
your patches to? For example, 'kernel@vger.kernel.org' doesn't exist
(maybe you meant linux-kernel@...).
I will not take patches that haven't been posted to LKML (and I
shouldn't have reviewed it the first place).
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-13 11:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 21:52 [PATCH v4 0/4] PCI EP driver support MSI doorbell from host Frank Li
2022-08-12 21:52 ` Frank Li
2022-08-12 21:52 ` [PATCH v4 1/4] irqchip: allow pass down .pm field at IRQCHIP_PLATFORM_DRIVER_END Frank Li
2022-08-12 21:52 ` Frank Li
2022-08-12 21:52 ` [PATCH v4 2/4] irqchip: imx mu worked as msi controller Frank Li
2022-08-12 21:52 ` Frank Li
2022-08-13 9:19 ` Marc Zyngier
2022-08-13 9:19 ` Marc Zyngier
2022-08-14 3:12 ` [EXT] " Frank Li
2022-08-14 3:12 ` Frank Li
2022-08-15 8:58 ` Marc Zyngier
2022-08-15 8:58 ` Marc Zyngier
2022-08-13 11:57 ` Marc Zyngier [this message]
2022-08-13 11:57 ` Marc Zyngier
2022-08-14 2:53 ` [EXT] " Frank Li
2022-08-14 2:53 ` Frank Li
2022-08-12 21:52 ` [PATCH v4 3/4] dt-bindings: irqchip: imx mu work " Frank Li
2022-08-12 21:52 ` Frank Li
2022-08-14 20:41 ` Rob Herring
2022-08-14 20:41 ` Rob Herring
2022-08-12 21:52 ` [PATCH v4 4/4] pcie: endpoint: pci-epf-vntb: add endpoint MSI support Frank Li
2022-08-12 21:52 ` 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=874jygs6e2.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-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lznuaa@gmail.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 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.