From: Niklas Cassel <niklas.cassel@axis.com>
To: Surender Polsani <surenderp@techveda.org>, <jespern@axis.com>,
<larper@axis.com>, <robh+dt@kernel.org>, <mark.rutland@arm.com>,
<linux@armlinux.org.uk>
Cc: <linux-arm-kernel@axis.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <sunil.m@techveda.org>
Subject: Re: [PATCH] arm: boot: dts: artpec6: Remove unnecessary interrupt-parent property from sub-nodes
Date: Mon, 4 Sep 2017 17:23:55 +0200 [thread overview]
Message-ID: <5310134e-c371-d43f-175f-a3a9cdc5b657@axis.com> (raw)
In-Reply-To: <8475266d-de55-0760-7ae4-9fcafead36e4@techveda.org>
On 08/11/2017 09:56 AM, Surender Polsani wrote:
> On Tuesday 27 June 2017 05:57 PM, Niklas Cassel wrote:
>> Acked-by: Niklas Cassel <niklas.cassel@axis.com>
>
> Hi Nik, This patch has been Acknowledged but is not getting added / applied to the
> respective git source tree. Please let me know if there is any problem.
Hello Surender,
Sorry for the delay.
Could you please resend your patch,
add "To: arm@kernel.org", together with my Ack.
Best regards,
Niklas
>
> Thanks
> Surender
>>
>> On 06/27/2017 02:15 PM, surenderp@techveda.org wrote:
>>> From: Surender Polsani <surenderp@techveda.org>
>>>
>>> "interrupt-parent" property is declared in root node, so it is global
>>> to all nodes. This property is re-declared in few sub-nodes. To avoid
>>> duplication this property is removed from following sub-nodes:
>>> pmu, amba@0, amba@0/ethernet.
>>>
>>> Signed-off-by: Surender Polsani <surenderp@techveda.org>
>>> ---
>>> arch/arm/boot/dts/artpec6.dtsi | 3 ---
>>> 1 file changed, 3 deletions(-)
>>>
>>> diff --git a/arch/arm/boot/dts/artpec6.dtsi b/arch/arm/boot/dts/artpec6.dtsi
>>> index 767cbe8..2ed1177 100644
>>> --- a/arch/arm/boot/dts/artpec6.dtsi
>>> +++ b/arch/arm/boot/dts/artpec6.dtsi
>>> @@ -151,7 +151,6 @@
>>> interrupts = <GIC_SPI 0 IRQ_TYPE_LEVEL_HIGH>,
>>> <GIC_SPI 1 IRQ_TYPE_LEVEL_HIGH>;
>>> interrupt-affinity = <&cpu0>, <&cpu1>;
>>> - interrupt-parent = <&intc>;
>>> };
>>> pcie: pcie@f8050000 {
>>> @@ -185,7 +184,6 @@
>>> compatible = "simple-bus";
>>> #address-cells = <0x1>;
>>> #size-cells = <0x1>;
>>> - interrupt-parent = <&intc>;
>>> ranges;
>>> dma-ranges = <0x80000000 0x00000000 0x40000000>;
>>> dma-coherent;
>>> @@ -195,7 +193,6 @@
>>> clocks = <ð_phy_ref_clk>,
>>> <&clkctrl ARTPEC6_CLK_ETH_ACLK>;
>>> compatible = "snps,dwc-qos-ethernet-4.10";
>>> - interrupt-parent = <&intc>;
>>> interrupts = <GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>;
>>> reg = <0xf8010000 0x4000>;
>>>
>
next prev parent reply other threads:[~2017-09-04 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 12:15 surenderp
2017-06-27 12:27 ` Niklas Cassel
2017-08-11 7:56 ` Surender Polsani
2017-09-04 15:23 ` Niklas Cassel [this message]
2017-09-06 5:08 ` [PATCH v2] arm: " surenderp
2017-10-19 21:25 ` [PATCH] arm: boot: " Arnd Bergmann
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=5310134e-c371-d43f-175f-a3a9cdc5b657@axis.com \
--to=niklas.cassel@axis.com \
--cc=devicetree@vger.kernel.org \
--cc=jespern@axis.com \
--cc=larper@axis.com \
--cc=linux-arm-kernel@axis.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sunil.m@techveda.org \
--cc=surenderp@techveda.org \
/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®