From: Nishanth Menon <nm@ti.com>
To: Andre Przywara <andre.przywara@arm.com>, Rob H <robh@kernel.org>
Cc: Michal Simek <michal.simek@xilinx.com>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>, Sekhar Nori <nsekhar@ti.com>,
<linux-kernel@vger.kernel.org>, Tero Kristo <kristo@kernel.org>,
Faiz Abbas <faiz_abbas@ti.com>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/4] arm64: dts: ti: k3: squelch warnings regarding no #address-cells for interrupt-controller
Date: Thu, 11 Mar 2021 16:01:09 -0600 [thread overview]
Message-ID: <20210311215914.pgpz2yymmfqlainl@episode> (raw)
In-Reply-To: <20210126163839.57491132@slackpad.fritz.box>
Andre, Rob,
On 16:38-20210126, Andre Przywara wrote:
> > Now that I look back at the dtc change, I'm now confused why this
> > check got applied. Both David and I wanted changes in regards to
> > #address-cells. Either a separate check or part of interrupt-map checks.
> > And the interrupt-map check never got applied. Andre?
>
> Yeah, I somewhat dropped the ball on this, after some iterations and a
> partial merge. Will put it on my list to revive this.
I was hoping we made some steps, but I did see [1] as well and it is
possible that I am missing some discussion, but it is starting to get
W=2 builds warnings noisy enough to start interfering with discovering
real problems as we keep adding new stuff in.. Just wondering...
[1] https://lore.kernel.org/linux-devicetree/CAL_Jsq++DyiKG9smQGx9FAPDJnVrezcXNb0Y5uh-5_2GBzTQpQ@mail.gmail.com/
[2] https://pastebin.ubuntu.com/p/ns6hPCBxVM/
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
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:[~2021-03-11 22:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 16:19 [PATCH v2 0/4] arm64: dts: ti: J7200 GPIO support and warning fixes Sekhar Nori
2020-11-17 16:19 ` [PATCH v2 1/4] arm64: dts: ti: k3: squelch warning about lack of #interrupt-cells Sekhar Nori
2020-11-17 16:19 ` [PATCH v2 2/4] arm64: dts: ti: k3: squelch warnings regarding no #address-cells for interrupt-controller Sekhar Nori
2020-11-18 11:38 ` Grygorii Strashko
2020-11-18 15:12 ` Nishanth Menon
2020-11-19 11:17 ` Grygorii Strashko
2020-11-19 13:28 ` Nishanth Menon
2020-11-23 4:15 ` Sekhar Nori
2020-11-24 1:21 ` Nishanth Menon
2020-11-24 4:16 ` Sekhar Nori
2020-11-27 14:23 ` Nishanth Menon
2021-01-08 14:05 ` Lokesh Vutla
2021-01-26 0:01 ` Rob Herring
2021-01-26 16:38 ` Andre Przywara
2021-03-11 22:01 ` Nishanth Menon [this message]
2020-11-17 16:19 ` [PATCH v2 3/4] arm64: dts: ti: k3-j7200: Add gpio nodes Sekhar Nori
2020-11-17 16:19 ` [PATCH v2 4/4] arm64: dts: ti: k3-j7200-common-proc-board: Disable unused gpio modules Sekhar Nori
2020-11-19 11:20 ` [PATCH v2 0/4] arm64: dts: ti: J7200 GPIO support and warning fixes Grygorii Strashko
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=20210311215914.pgpz2yymmfqlainl@episode \
--to=nm@ti.com \
--cc=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=michal.simek@xilinx.com \
--cc=nsekhar@ti.com \
--cc=robh@kernel.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