From: Conor Dooley <conor@kernel.org>
To: Samuel Holland <samuel.holland@sifive.com>
Cc: linux-riscv@lists.infradead.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH] riscv: dts: sifive: add missing #interrupt-cells to pmic
Date: Wed, 14 Feb 2024 09:10:46 +0000 [thread overview]
Message-ID: <20240214-stoplight-banjo-b446d2d322f2@spud> (raw)
In-Reply-To: <4854dbc3-7c35-432d-b991-0951496eaa2b@sifive.com>
[-- Attachment #1.1: Type: text/plain, Size: 650 bytes --]
On Tue, Feb 13, 2024 at 03:49:53PM -0600, Samuel Holland wrote:
> On 2024-02-13 1:47 PM, Conor Dooley wrote:
> > From: Conor Dooley <conor.dooley@microchip.com>
> >
> > At W=2 dtc complains:
> > hifive-unmatched-a00.dts:120.10-238.4: Warning (interrupt_provider): /soc/i2c@10030000/pmic@58: Missing '#interrupt-cells' in interrupt provider
> >
> > Add the missing property.
> >
> > Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> > ---
> > arch/riscv/boot/dts/sifive/hifive-unmatched-a00.dts | 1 +
> > 1 file changed, 1 insertion(+)
>
> Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
Applied so, thanks :)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-02-14 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 19:47 [PATCH] riscv: dts: sifive: add missing #interrupt-cells to pmic Conor Dooley
2024-02-13 21:49 ` Samuel Holland
2024-02-14 9:10 ` Conor Dooley [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=20240214-stoplight-banjo-b446d2d322f2@spud \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=linux-riscv@lists.infradead.org \
--cc=samuel.holland@sifive.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