From: Nishanth Menon <nm@ti.com>
To: Nishanth Menon <nm@ti.com>, Jyri Sarha <jsarha@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, Tero Kristo <t-kristo@ti.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am65*/j721e*: Fix unit address format error for dss node
Date: Thu, 12 Nov 2020 11:49:47 -0600 [thread overview]
Message-ID: <160520334646.32099.14700006889822452477.b4-ty@ti.com> (raw)
In-Reply-To: <20201104222519.12308-1-nm@ti.com>
On Wed, 4 Nov 2020 16:25:19 -0600, Nishanth Menon wrote:
> Fix the node address to follow the device tree convention.
>
> This fixes the dtc warning:
> <stdout>: Warning (simple_bus_reg): /bus@100000/dss@04a00000: simple-bus
> unit address format error, expected "4a00000"
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-am65*/j721e*: Fix unit address format error for dss node
commit: cfbf17e69ae82f647c287366b7573e532fc281ee
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] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Nishanth Menon <nm@ti.com>, Jyri Sarha <jsarha@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: ti: k3-am65*/j721e*: Fix unit address format error for dss node
Date: Thu, 12 Nov 2020 11:49:47 -0600 [thread overview]
Message-ID: <160520334646.32099.14700006889822452477.b4-ty@ti.com> (raw)
In-Reply-To: <20201104222519.12308-1-nm@ti.com>
On Wed, 4 Nov 2020 16:25:19 -0600, Nishanth Menon wrote:
> Fix the node address to follow the device tree convention.
>
> This fixes the dtc warning:
> <stdout>: Warning (simple_bus_reg): /bus@100000/dss@04a00000: simple-bus
> unit address format error, expected "4a00000"
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-am65*/j721e*: Fix unit address format error for dss node
commit: cfbf17e69ae82f647c287366b7573e532fc281ee
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] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
--
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:[~2020-11-12 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 22:25 [PATCH] arm64: dts: ti: k3-am65*/j721e*: Fix unit address format error for dss node Nishanth Menon
2020-11-04 22:25 ` Nishanth Menon
2020-11-04 22:27 ` Jyri Sarha
2020-11-04 22:27 ` Jyri Sarha
2020-11-05 7:19 ` Tomi Valkeinen
2020-11-05 7:19 ` Tomi Valkeinen
2020-11-12 17:49 ` Nishanth Menon [this message]
2020-11-12 17:49 ` Nishanth Menon
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=160520334646.32099.14700006889822452477.b4-ty@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jsarha@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tomi.valkeinen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.