From: Rob Herring <robh@kernel.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: linux-arm-kernel@lists.infradead.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-mediatek@lists.infradead.org,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>
Subject: Re: [PATCH next v2] dt-bindings: nvmem: convert mtk-efuse.txt to YAML schema
Date: Tue, 21 Dec 2021 15:48:14 -0400 [thread overview]
Message-ID: <YcIvfkynRGRqQR2X@robh.at.kernel.org> (raw)
In-Reply-To: <20211218081515.4971-1-chunfeng.yun@mediatek.com>
On Sat, 18 Dec 2021 16:15:15 +0800, Chunfeng Yun wrote:
> Convert mtk-efuse.txt to YAML schema mediatek,efuse.yaml
>
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> ---
> v2:
> 1. remove description of subnodes which is covered by nvmem.yaml suggested by Rob
> 2. change the example which is commoner than mt8173's
>
> ---
> .../bindings/nvmem/mediatek,efuse.yaml | 86 +++++++++++++++++++
> .../devicetree/bindings/nvmem/mtk-efuse.txt | 43 ----------
> 2 files changed, 86 insertions(+), 43 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> delete mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: linux-arm-kernel@lists.infradead.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-mediatek@lists.infradead.org,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>
Subject: Re: [PATCH next v2] dt-bindings: nvmem: convert mtk-efuse.txt to YAML schema
Date: Tue, 21 Dec 2021 15:48:14 -0400 [thread overview]
Message-ID: <YcIvfkynRGRqQR2X@robh.at.kernel.org> (raw)
In-Reply-To: <20211218081515.4971-1-chunfeng.yun@mediatek.com>
On Sat, 18 Dec 2021 16:15:15 +0800, Chunfeng Yun wrote:
> Convert mtk-efuse.txt to YAML schema mediatek,efuse.yaml
>
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> ---
> v2:
> 1. remove description of subnodes which is covered by nvmem.yaml suggested by Rob
> 2. change the example which is commoner than mt8173's
>
> ---
> .../bindings/nvmem/mediatek,efuse.yaml | 86 +++++++++++++++++++
> .../devicetree/bindings/nvmem/mtk-efuse.txt | 43 ----------
> 2 files changed, 86 insertions(+), 43 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> delete mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: linux-arm-kernel@lists.infradead.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-mediatek@lists.infradead.org,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>
Subject: Re: [PATCH next v2] dt-bindings: nvmem: convert mtk-efuse.txt to YAML schema
Date: Tue, 21 Dec 2021 15:48:14 -0400 [thread overview]
Message-ID: <YcIvfkynRGRqQR2X@robh.at.kernel.org> (raw)
In-Reply-To: <20211218081515.4971-1-chunfeng.yun@mediatek.com>
On Sat, 18 Dec 2021 16:15:15 +0800, Chunfeng Yun wrote:
> Convert mtk-efuse.txt to YAML schema mediatek,efuse.yaml
>
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> ---
> v2:
> 1. remove description of subnodes which is covered by nvmem.yaml suggested by Rob
> 2. change the example which is commoner than mt8173's
>
> ---
> .../bindings/nvmem/mediatek,efuse.yaml | 86 +++++++++++++++++++
> .../devicetree/bindings/nvmem/mtk-efuse.txt | 43 ----------
> 2 files changed, 86 insertions(+), 43 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
> delete mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-12-21 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 8:15 [PATCH next v2] dt-bindings: nvmem: convert mtk-efuse.txt to YAML schema Chunfeng Yun
2021-12-18 8:15 ` Chunfeng Yun
2021-12-18 8:15 ` Chunfeng Yun
2021-12-21 19:48 ` Rob Herring [this message]
2021-12-21 19:48 ` Rob Herring
2021-12-21 19:48 ` 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=YcIvfkynRGRqQR2X@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=chunfeng.yun@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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 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.