All of lore.kernel.org
 help / color / mirror / Atom feed
From: allen-kh.cheng <allen-kh.cheng@mediatek.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>
Cc: Lala Lin <lala.lin@mediatek.com>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>,
	Chen-Yu Tsai <wenst@chromium.org>,
	Allen-kh Cheng <allen-kh.cheng@mediatek.corp-partner.google.com>,
	Chunfeng Yun <chunfeng.yun@mediatek.com>
Subject: Re: [PATCH v4 0/3] dt-bindings: nvmem: mediatek: Convert efuse binding to YAML
Date: Wed, 11 May 2022 10:43:14 +0800	[thread overview]
Message-ID: <73b1feab3ecb20fef0339b322a61d63146b5790a.camel@mediatek.com> (raw)
In-Reply-To: <20220510132637.5864-1-allen-kh.cheng@mediatek.com>

Hi the reviewers,

Please ignore this PATCH series.

There is anther series for efuse yaml (
20220509014521.10248-1-chunfeng.yun@mediatek.com) by chunfeng.

We will integrate together and resend again.

I apologize for any inconvenience caused.

Best regard,
Allen

On Tue, 2022-05-10 at 21:26 +0800, Allen-KH Cheng wrote:
> From: Allen-kh Cheng <allen-kh.cheng@mediatek.corp-partner.google.com
> >
> 
> Convert MediaTek eFuse devicetree binding to YAML.
> 
> Based on tag: next-20220510, linux-next/master
> 
> Run cmds as following:
> make DT_CHECKER_FLAGS=-m dt_binding_check
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/nvmem/mediatek,efus
> e.yaml
> 
> make ARCH=arm64
> dtbs_check
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/nvmem/mediatek,efus
> e.yaml
> 
> We mark the mediatek,mt8173-efuse and mediatek,efuse as deprecated to
> indicate
> not use a signle compatible and should always use mediatek,efuse as
> generic
> fallback.
> 
> change since v3:
>  - use mediatek as vendor name instead of mtk
> 
> changes since v2:
>  - document deprecated efuse property
>  - update efuse compatible fallbacks
>  - add two PATCHs into series
> 
> changes since v1:
> - change file name from mtk,efuse-yaml to mtk,efuse.yaml
> - add efuse in commit title
> - change compatible entries from const to enum
> 
> Allen-KH Cheng (2):
>   dt-bindings: nvmem: mediatek: Convert efuse binding to YAML
>   arm64: dts: mediatek: update efuse compatible fallbacks
> 
> Allen-kh Cheng (1):
>   dt-bindings: nvmem: mediatek: document deprecated efuse property
> 
>  .../bindings/nvmem/mediatek,efuse.yaml        | 60
> +++++++++++++++++++
>  .../devicetree/bindings/nvmem/mtk-efuse.txt   | 43 -------------
>  arch/arm64/boot/dts/mediatek/mt8173.dtsi      |  3 +-
>  arch/arm64/boot/dts/mediatek/mt8192.dtsi      |  3 +-
>  4 files changed, 64 insertions(+), 45 deletions(-)
>  create mode 100644
> Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
>  delete mode 100644 Documentation/devicetree/bindings/nvmem/mtk-
> efuse.txt
> 


_______________________________________________
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: allen-kh.cheng <allen-kh.cheng@mediatek.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>
Cc: Lala Lin <lala.lin@mediatek.com>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>,
	Chen-Yu Tsai <wenst@chromium.org>,
	Allen-kh Cheng <allen-kh.cheng@mediatek.corp-partner.google.com>,
	Chunfeng Yun <chunfeng.yun@mediatek.com>
Subject: Re: [PATCH v4 0/3] dt-bindings: nvmem: mediatek: Convert efuse binding to YAML
Date: Wed, 11 May 2022 10:43:14 +0800	[thread overview]
Message-ID: <73b1feab3ecb20fef0339b322a61d63146b5790a.camel@mediatek.com> (raw)
In-Reply-To: <20220510132637.5864-1-allen-kh.cheng@mediatek.com>

Hi the reviewers,

Please ignore this PATCH series.

There is anther series for efuse yaml (
20220509014521.10248-1-chunfeng.yun@mediatek.com) by chunfeng.

We will integrate together and resend again.

I apologize for any inconvenience caused.

Best regard,
Allen

On Tue, 2022-05-10 at 21:26 +0800, Allen-KH Cheng wrote:
> From: Allen-kh Cheng <allen-kh.cheng@mediatek.corp-partner.google.com
> >
> 
> Convert MediaTek eFuse devicetree binding to YAML.
> 
> Based on tag: next-20220510, linux-next/master
> 
> Run cmds as following:
> make DT_CHECKER_FLAGS=-m dt_binding_check
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/nvmem/mediatek,efus
> e.yaml
> 
> make ARCH=arm64
> dtbs_check
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/nvmem/mediatek,efus
> e.yaml
> 
> We mark the mediatek,mt8173-efuse and mediatek,efuse as deprecated to
> indicate
> not use a signle compatible and should always use mediatek,efuse as
> generic
> fallback.
> 
> change since v3:
>  - use mediatek as vendor name instead of mtk
> 
> changes since v2:
>  - document deprecated efuse property
>  - update efuse compatible fallbacks
>  - add two PATCHs into series
> 
> changes since v1:
> - change file name from mtk,efuse-yaml to mtk,efuse.yaml
> - add efuse in commit title
> - change compatible entries from const to enum
> 
> Allen-KH Cheng (2):
>   dt-bindings: nvmem: mediatek: Convert efuse binding to YAML
>   arm64: dts: mediatek: update efuse compatible fallbacks
> 
> Allen-kh Cheng (1):
>   dt-bindings: nvmem: mediatek: document deprecated efuse property
> 
>  .../bindings/nvmem/mediatek,efuse.yaml        | 60
> +++++++++++++++++++
>  .../devicetree/bindings/nvmem/mtk-efuse.txt   | 43 -------------
>  arch/arm64/boot/dts/mediatek/mt8173.dtsi      |  3 +-
>  arch/arm64/boot/dts/mediatek/mt8192.dtsi      |  3 +-
>  4 files changed, 64 insertions(+), 45 deletions(-)
>  create mode 100644
> Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml
>  delete mode 100644 Documentation/devicetree/bindings/nvmem/mtk-
> efuse.txt
> 


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-05-11  2:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 13:26 [PATCH v4 0/3] dt-bindings: nvmem: mediatek: Convert efuse binding to YAML Allen-KH Cheng
2022-05-10 13:26 ` Allen-KH Cheng
2022-05-10 13:26 ` Allen-KH Cheng
2022-05-10 13:26 ` [PATCH v4 1/3] " Allen-KH Cheng
2022-05-10 13:26   ` Allen-KH Cheng
2022-05-10 13:26   ` Allen-KH Cheng
2022-05-11 15:16   ` Krzysztof Kozlowski
2022-05-11 15:16     ` Krzysztof Kozlowski
2022-05-11 15:16     ` Krzysztof Kozlowski
2022-05-10 13:26 ` [PATCH v4 2/3] dt-bindings: nvmem: mediatek: document deprecated efuse property Allen-KH Cheng
2022-05-10 13:26   ` Allen-KH Cheng
2022-05-10 13:26   ` Allen-KH Cheng
2022-05-11 15:20   ` Krzysztof Kozlowski
2022-05-11 15:20     ` Krzysztof Kozlowski
2022-05-11 15:20     ` Krzysztof Kozlowski
2022-05-12  2:13     ` allen-kh.cheng
2022-05-12  2:13       ` allen-kh.cheng
2022-05-10 13:26 ` [PATCH v4 3/3] arm64: dts: mediatek: update efuse compatible fallbacks Allen-KH Cheng
2022-05-10 13:26   ` Allen-KH Cheng
2022-05-10 13:26   ` Allen-KH Cheng
2022-05-11  2:43 ` allen-kh.cheng [this message]
2022-05-11  2:43   ` [PATCH v4 0/3] dt-bindings: nvmem: mediatek: Convert efuse binding to YAML allen-kh.cheng

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=73b1feab3ecb20fef0339b322a61d63146b5790a.camel@mediatek.com \
    --to=allen-kh.cheng@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=allen-kh.cheng@mediatek.corp-partner.google.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=lala.lin@mediatek.com \
    --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 \
    --cc=wenst@chromium.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.