From: Andrew Lunn <andrew@lunn.ch>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Gregory Clement" <gregory.clement@bootlin.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Marek Behún" <kabel@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] ARM: dts: mvebu: Add definitions for PCIe legacy INTx interrupts
Date: Wed, 6 Jul 2022 22:53:46 +0200 [thread overview]
Message-ID: <YsX2Wvtz7hEpJ6X+@lunn.ch> (raw)
In-Reply-To: <20220706183114.30783-1-pali@kernel.org>
On Wed, Jul 06, 2022 at 08:31:03PM +0200, Pali Rohár wrote:
> This patch series add definitions for PCIe legacy INTx interrupts into
> every DTS file used by the pci-mvebu.c controller driver.
What you fail to explain in the commit message is Why?
Andrew
next prev parent reply other threads:[~2022-07-06 20:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 18:31 Pali Rohár
2022-07-06 18:31 ` [PATCH 01/11] ARM: dts: kirkwood: " Pali Rohár
2022-07-06 18:31 ` [PATCH 02/11] ARM: dts: dove: " Pali Rohár
2022-07-06 18:31 ` [PATCH 03/11] ARM: dts: armada-370.dtsi: " Pali Rohár
2022-07-06 18:31 ` [PATCH 04/11] ARM: dts: armada-xp-98dx3236.dtsi: " Pali Rohár
2022-07-06 18:31 ` [PATCH 05/11] ARM: dts: armada-xp-mv78230.dtsi: " Pali Rohár
2022-07-06 18:31 ` [PATCH 06/11] ARM: dts: armada-xp-mv78260.dtsi: " Pali Rohár
2022-07-06 18:31 ` [PATCH 07/11] ARM: dts: armada-xp-mv78460.dtsi: " Pali Rohár
2022-07-06 18:31 ` [PATCH 08/11] ARM: dts: armada-375.dtsi: " Pali Rohár
2022-07-06 18:31 ` [PATCH 09/11] ARM: dts: armada-380.dtsi: " Pali Rohár
2022-07-06 18:31 ` [PATCH 10/11] ARM: dts: armada-385.dtsi: " Pali Rohár
2022-07-06 18:31 ` [PATCH 11/11] ARM: dts: armada-39x.dtsi: " Pali Rohár
2022-07-06 20:53 ` Andrew Lunn [this message]
2022-07-07 14:38 ` [PATCH 00/11] ARM: dts: mvebu: " Marek Behún
2022-07-07 16:50 ` Andrew Lunn
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=YsX2Wvtz7hEpJ6X+@lunn.ch \
--to=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
/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
all inboxes | Powered by JetHome®