From: Nishanth Menon <nm@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Andrew Davis <afd@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] arm64: dts: ti: k3-am65: Use exact ranges for FSS node
Date: Fri, 26 Apr 2024 17:37:21 -0500 [thread overview]
Message-ID: <171417102550.3482062.1616101241058926180.b4-ty@ti.com> (raw)
In-Reply-To: <20240326205920.40147-1-afd@ti.com>
Hi Andrew Davis,
On Tue, 26 Mar 2024 15:59:17 -0500, Andrew Davis wrote:
> The FSS bus contains several register ranges. Using an empty
> ranges property works but causes a DT warning when we give
> this node an address. Fix this by explicitly defining the
> memory ranges in use.
>
>
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/4] arm64: dts: ti: k3-am65: Use exact ranges for FSS node
commit: 8ec19dbe9217edbb564b16a5f68465b8cd42a167
[2/4] arm64: dts: ti: k3-j7200: Use exact ranges for FSS node
commit: 98b939a9b3204120bd3a96015d74cbe818a3a2e9
[3/4] arm64: dts: ti: k3-j721e: Use exact ranges for FSS node
commit: 74904fc1f1f1c802eaed10edc3744f0997c154ff
[4/4] arm64: dts: ti: k3-j784s4: Use exact ranges for FSS node
commit: b3f629482cade3a6ada44d2e83dd65f0f1ed1293
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2024-04-26 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 20:59 [PATCH 1/4] arm64: dts: ti: k3-am65: Use exact ranges for FSS node Andrew Davis
2024-03-26 20:59 ` [PATCH 2/4] arm64: dts: ti: k3-j7200: " Andrew Davis
2024-03-26 20:59 ` [PATCH 3/4] arm64: dts: ti: k3-j721e: " Andrew Davis
2024-03-26 20:59 ` [PATCH 4/4] arm64: dts: ti: k3-j784s4: " Andrew Davis
2024-04-26 22:37 ` Nishanth Menon [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=171417102550.3482062.1616101241058926180.b4-ty@ti.com \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).