From: Yanteng Si <siyanteng@loongson.cn>
To: Baruch Siach <baruch@tkos.co.il>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Alex Shi <alexs@kernel.org>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 2/2] docs: zh_CN/devicetree: sync usage-model fix
Date: Thu, 27 Apr 2023 21:28:35 +0800 [thread overview]
Message-ID: <ffa08a81-3a66-d4b9-99ee-a0d0f349ad85@loongson.cn> (raw)
In-Reply-To: <b39560250cb58f8cdcfe95791ce5af7455c6e8e3.1682333574.git.baruch@tkos.co.il>
在 4/24/23 18:52, Baruch Siach 写道:
> Sync compatibly string fix from the English document.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Reviewed-by: Yanteng Si <siyanteng@loongson.cn>
Thanks,
Yanteng
> ---
> v2:
>
> New separate patch for translation
> ---
> Documentation/translations/zh_CN/devicetree/usage-model.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_CN/devicetree/usage-model.rst b/Documentation/translations/zh_CN/devicetree/usage-model.rst
> index c6aee82c7e6e..19ba4ae0cd81 100644
> --- a/Documentation/translations/zh_CN/devicetree/usage-model.rst
> +++ b/Documentation/translations/zh_CN/devicetree/usage-model.rst
> @@ -325,6 +325,6 @@ Primecell设备。然而,棘手的一点是,AMBA总线上的所有设备并
>
> 当使用DT时,这给of_platform_populate()带来了问题,因为它必须决定是否将
> 每个节点注册为platform_device或amba_device。不幸的是,这使设备创建模型
> -变得有点复杂,但解决方案原来并不是太具有侵略性。如果一个节点与“arm,amba-primecell”
> +变得有点复杂,但解决方案原来并不是太具有侵略性。如果一个节点与“arm,primecell”
> 兼容,那么of_platform_populate()将把它注册为amba_device而不是
> platform_device。
next prev parent reply other threads:[~2023-04-27 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 10:52 [PATCH v2 1/2] docs: dt: fix documented Primecell compatible string Baruch Siach
2023-04-24 10:52 ` [PATCH v2 2/2] docs: zh_CN/devicetree: sync usage-model fix Baruch Siach
2023-04-27 13:28 ` Yanteng Si [this message]
2023-04-25 8:31 ` [PATCH v2 1/2] docs: dt: fix documented Primecell compatible string Baruch Siach
2023-05-01 9:53 ` Krzysztof Kozlowski
2023-05-01 10:01 ` Baruch Siach
2023-05-01 12:09 ` Krzysztof Kozlowski
2023-05-09 8:36 ` Baruch Siach
2023-06-08 13:31 ` Rob Herring
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=ffa08a81-3a66-d4b9-99ee-a0d0f349ad85@loongson.cn \
--to=siyanteng@loongson.cn \
--cc=alexs@kernel.org \
--cc=baruch@tkos.co.il \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=robh+dt@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).