From: Vineet Gupta <vgupta@kernel.org>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: arcml <linux-snps-arc@lists.infradead.org>,
Pavel Kozlov <Pavel.Kozlov@synopsys.com>
Subject: Re: recent kernel warning
Date: Thu, 28 Mar 2024 13:21:46 -0700 [thread overview]
Message-ID: <92b93599-4ce8-499d-a944-3991e42b6e0a@kernel.org> (raw)
In-Reply-To: <DS7PR12MB9041525EAB9D5FAE1B13D056A13B2@DS7PR12MB9041.namprd12.prod.outlook.com>
On 3/28/24 11:01, Alexey Brodkin wrote:
> Hi Vineet,
>
> Indeed, it's incorrect placement of "#interrupt-cells" in the Ethernet
> controller node.
> I'll remove it and will send out a patch with the fix.
And while at it please audit all the DTs in arch/arc
Thx,
-Vineet
>
> Thanks for the pointer.
>
> -Alexey
> ------------------------------------------------------------------------
> *From:* Vineet Gupta <vgupta@kernel.org>
> *Sent:* Thursday, March 28, 2024 5:15 AM
> *To:* Alexey Brodkin <abrodkin@synopsys.com>; arcml
> <linux-snps-arc@lists.infradead.org>
> *Subject:* recent kernel warning
>
> Alexey,
>
> Can you have someone look at the following kernel warning:
>
> DTC arch/arc/boot/dts/hsdk.dtb
> ../arch/arc/boot/dts/hsdk.dts:207.23-235.5: Warning
> (interrupt_provider): /soc/ethernet@8000: '#interrupt-cells' found, but
> node is not an interrupt provider
> arch/arc/boot/dts/hsdk.dtb: Warning (interrupt_map): Failed prerequisite
> 'interrupt_provider'
>
> Thx,
> -Vineet
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
prev parent reply other threads:[~2024-03-28 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 5:15 recent kernel warning Vineet Gupta
[not found] ` <DS7PR12MB9041525EAB9D5FAE1B13D056A13B2@DS7PR12MB9041.namprd12.prod.outlook.com>
2024-03-28 20:21 ` Vineet Gupta [this message]
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=92b93599-4ce8-499d-a944-3991e42b6e0a@kernel.org \
--to=vgupta@kernel.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Pavel.Kozlov@synopsys.com \
--cc=linux-snps-arc@lists.infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).