LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tinghan Shen <tinghan.shen@mediatek.com>
To: <ohad@wizery.com>, <bjorn.andersson@linaro.org>,
	<mathieu.poirier@linaro.org>, <robh+dt@kernel.org>,
	<matthias.bgg@gmail.com>, <krzysztof.kozlowski@canonical.com>,
	<shawnguo@kernel.org>, <sam@ravnborg.org>,
	<linux@rempel-privat.de>, <daniel@0x0f.com>,
	<Max.Merchel@tq-group.com>, <geert+renesas@glider.be>,
	<fanghao11@huawei.com>
Cc: <linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Tinghan Shen <tinghan.shen@mediatek.com>
Subject: [PATCH v6 5/6] rpmsg: change naming of mediatek rpmsg property
Date: Mon, 9 Aug 2021 13:19:58 +0800	[thread overview]
Message-ID: <20210809051959.31136-6-tinghan.shen@mediatek.com> (raw)
In-Reply-To: <20210809051959.31136-1-tinghan.shen@mediatek.com>

Change from "mtk,rpmsg-name" to "mediatek,rpmsg-name" to sync with the
vendor name defined in vendor-prefixes.yaml.

Signed-off-by: Tinghan Shen <tinghan.shen@mediatek.com>
---
 drivers/rpmsg/mtk_rpmsg.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/rpmsg/mtk_rpmsg.c b/drivers/rpmsg/mtk_rpmsg.c
index 96a17ec29140..5b4404b8be4c 100644
--- a/drivers/rpmsg/mtk_rpmsg.c
+++ b/drivers/rpmsg/mtk_rpmsg.c
@@ -183,7 +183,7 @@ mtk_rpmsg_match_device_subnode(struct device_node *node, const char *channel)
 	int ret;
 
 	for_each_available_child_of_node(node, child) {
-		ret = of_property_read_string(child, "mtk,rpmsg-name", &name);
+		ret = of_property_read_string(child, "mediatek,rpmsg-name", &name);
 		if (ret)
 			continue;
 
-- 
2.18.0


  parent reply	other threads:[~2021-08-09  5:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09  5:19 [PATCH v6 0/6] Mediatek MT8195 SCP support Tinghan Shen
2021-08-09  5:19 ` [PATCH v6 1/6] dt-bindings: remoteproc: mediatek: Add binding for mt8195 scp Tinghan Shen
2021-08-09  5:19 ` [PATCH v6 2/6] dt-bindings: remoteproc: mediatek: Add binding for mt8192 scp Tinghan Shen
2021-08-09  5:19 ` [PATCH v6 3/6] dt-bindings: remoteproc: mediatek: Convert mtk,scp to json-schema Tinghan Shen
2021-08-13 20:57   ` Rob Herring
2021-08-09  5:19 ` [PATCH v6 4/6] remoteproc: mediatek: Support mt8195 scp Tinghan Shen
2021-08-09  5:19 ` Tinghan Shen [this message]
2021-08-09  5:19 ` [PATCH v6 6/6] arm64: dts: mt8183: change rpmsg property name Tinghan Shen

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=20210809051959.31136-6-tinghan.shen@mediatek.com \
    --to=tinghan.shen@mediatek.com \
    --cc=Max.Merchel@tq-group.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=daniel@0x0f.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fanghao11@huawei.com \
    --cc=geert+renesas@glider.be \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=mathieu.poirier@linaro.org \
    --cc=matthias.bgg@gmail.com \
    --cc=ohad@wizery.com \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=shawnguo@kernel.org \
    --subject='Re: [PATCH v6 5/6] rpmsg: change naming of mediatek rpmsg property' \
    /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

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).