linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Nishanth Menon <nm@ti.com>, Santosh Shilimkar <ssantosh@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: keystone-k2g: Rename message-manager node
Date: Mon, 19 Apr 2021 09:50:01 -0500	[thread overview]
Message-ID: <e52fe654-a9b7-ca49-d501-1dd01159c787@ti.com> (raw)
In-Reply-To: <20210414001926.20002-1-nm@ti.com>

On 4/13/21 7:19 PM, Nishanth Menon wrote:
> Rename message-manager instance node name to be better aligned with
> current style of device tree nodes for mailboxes.
> 
> Signed-off-by: Nishanth Menon <nm@ti.com>

Acked-by: Suman Anna <s-anna@ti.com>

> ---
> 
> Santosh:
> - This is'nt critical to queue up for 5.13-rc1 window, but just getting
>   it out of the way. I noticed it as I was converting the binding to
>   yaml. (patch for yaml conversion for the node follows)
> 
>  arch/arm/boot/dts/keystone-k2g.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/keystone-k2g.dtsi b/arch/arm/boot/dts/keystone-k2g.dtsi
> index 05a75019275e..e5c813b5556d 100644
> --- a/arch/arm/boot/dts/keystone-k2g.dtsi
> +++ b/arch/arm/boot/dts/keystone-k2g.dtsi
> @@ -242,7 +242,7 @@ dsp0: dsp@10800000 {
>  			status = "disabled";
>  		};
>  
> -		msgmgr: msgmgr@2a00000 {
> +		msgmgr: mailbox@2a00000 {
>  			compatible = "ti,k2g-message-manager";
>  			#mbox-cells = <2>;
>  			reg-names = "queue_proxy_region",
> 


      reply	other threads:[~2021-04-19 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14  0:19 [PATCH] ARM: dts: keystone-k2g: Rename message-manager node Nishanth Menon
2021-04-19 14:50 ` Suman Anna [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=e52fe654-a9b7-ca49-d501-1dd01159c787@ti.com \
    --to=s-anna@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=ssantosh@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;
as well as URLs for NNTP newsgroup(s).