From: Sudeep Holla <sudeep.holla@arm.com>
To: jassisinghbrar@gmail.com
Cc: robh@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>,
Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCH] arm64: dts: juno: Add missing MHU secure-irq
Date: Mon, 1 Aug 2022 11:38:03 +0100 [thread overview]
Message-ID: <20220801103803.5fyftr4jbgfvim7l@bogus> (raw)
In-Reply-To: <20220801103308.yehh7l6k4fmrxlqh@bogus>
On Mon, Aug 01, 2022 at 11:33:08AM +0100, Sudeep Holla wrote:
> On Sat, Jul 30, 2022 at 09:23:36AM -0500, jassisinghbrar@gmail.com wrote:
> > From: Jassi Brar <jaswinder.singh@linaro.org>
> >
> > The MHU secure interrupt exists physically but is missing in the DT node.
> >
> > Specify the interrupt in DT node to fix a warning on Arm Juno board:
> > mhu@2b1f0000: interrupts: [[0, 36, 4], [0, 35, 4]] is too short
> >
>
> It fails to apply on v5.18-rc1 or v5.19. Can you please rebase and resend ?
>
Sorry I meant v5.19-rc1 or v5.19 as my -next branch is based on the former.
IIUC the interrupt-names are dropped couple of release back as it was not
in the binding.
--
Regards,
Sudeep
next prev parent reply other threads:[~2022-08-01 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 14:23 [PATCH] arm64: dts: juno: Add missing MHU secure-irq jassisinghbrar
2022-08-01 10:33 ` Sudeep Holla
2022-08-01 10:38 ` Sudeep Holla [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-01 14:10 jassisinghbrar
2022-08-15 14:24 ` Sudeep Holla
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=20220801103803.5fyftr4jbgfvim7l@bogus \
--to=sudeep.holla@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=jaswinder.singh@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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