From: Conor Dooley <conor@kernel.org>
To: Stanislav Jakubek <stano.jakubek@gmail.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Baolin Wang <baolin.wang7@gmail.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
Yanxin Huang <yanxin.huang@unisoc.com>,
huang yanxin <yanxin.huang07@gmail.com>,
Wenming Wu <wenming.wu@unisoc.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: nvmem: sprd,ums312-efuse: convert to YAML
Date: Wed, 17 Jul 2024 15:22:26 +0100 [thread overview]
Message-ID: <20240717-cartwheel-kangaroo-2a1fcc140d7c@spud> (raw)
In-Reply-To: <17ccb895a54d7754d3ddd6de633ad045a5271b4b.1721199034.git.stano.jakubek@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
On Wed, Jul 17, 2024 at 08:55:14AM +0200, Stanislav Jakubek wrote:
> Convert the Spreadtrum UMS312 eFuse bindings to DT schema.
> Adjust filename to match compatible.
>
> Note: the UMS312 clock bindings include doesn't seem to exist (yet?), so
> the UMS512 one was used for the "CLK_EFUSE_EB" define.
The example is literally just that, there's no need to use the defines
at all.
This looks fine to me though,
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-07-17 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 6:54 [PATCH v2 1/2] dt-bindings: nvmem: sprd,sc2731-efuse: convert to YAML Stanislav Jakubek
2024-07-17 6:55 ` [PATCH v2 2/2] dt-bindings: nvmem: sprd,ums312-efuse: " Stanislav Jakubek
2024-07-17 14:22 ` Conor Dooley [this message]
2024-07-17 14:24 ` [PATCH v2 1/2] dt-bindings: nvmem: sprd,sc2731-efuse: " Conor Dooley
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=20240717-cartwheel-kangaroo-2a1fcc140d7c@spud \
--to=conor@kernel.org \
--cc=baolin.wang7@gmail.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stano.jakubek@gmail.com \
--cc=wenming.wu@unisoc.com \
--cc=yanxin.huang07@gmail.com \
--cc=yanxin.huang@unisoc.com \
--cc=zhang.lyra@gmail.com \
/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