From: Saalim Quadri <danascape@gmail.com>
To: krzysztof.kozlowski@linaro.org
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
danascape@gmail.com, daniel.baluta@nxp.com,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com, robh+dt@kernel.org
Subject: [PATCH] ASoC: dt-bindings: wm8753: Convert to dtschema
Date: Sat, 15 Apr 2023 20:12:46 +0000 [thread overview]
Message-ID: <20230415201246.1200683-1-danascape@gmail.com> (raw)
In-Reply-To: <5d629ff3-c5ae-bd00-e70d-8c0d58365ce3@linaro.org>
> You choose unusual bindings to convert to DT schema. It is fine but
> honestly, less useful, with limited impact. This is an old, 12 year old
> binding without users. Maybe it would be even removed by now...
> I suggest converting ones which have a real impact - have users in DTS.
> Otherwise you will be putting quite a lot of effort for no real gains...
> because what is the difference between this binding being TXT and DT schema?
I am converting these bindings as part of my GSoC project where I need to convert
as many files as possible during the given tenure, I am slowly trying to read files
in other subsystems too and will push patches for other subsystems too.
Is it fine?
About the part where you suggested to convert the txt into a single YAML, shall I
continue working on them? As I can see Mark merged the previous 2 patches to linux-next
Kind Regards,
Saalim
next prev parent reply other threads:[~2023-04-15 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 22:38 [PATCH] ASoC: dt-bindings: wm8753: Convert to dtschema Saalim Quadri
2023-04-15 9:16 ` Krzysztof Kozlowski
2023-04-15 20:12 ` Saalim Quadri [this message]
2023-04-16 7:35 ` Krzysztof Kozlowski
2023-04-16 18:51 ` Krzysztof Kozlowski
2023-04-17 20:46 ` Saalim Quadri
2023-04-17 9:15 ` Charles Keepax
2023-04-17 19:28 ` Mark Brown
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=20230415201246.1200683-1-danascape@gmail.com \
--to=danascape@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--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).