From: Rob Herring <robh@kernel.org>
To: Sameer Pujar <spujar@nvidia.com>
Cc: alsa-devel@alsa-project.org, stephan@gerhold.net,
lgirdwood@gmail.com, jbrunet@baylibre.com,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, broonie@kernel.org,
thierry.reding@gmail.com, jonathanh@nvidia.com,
robh+dt@kernel.org
Subject: Re: [PATCH v3 1/3] ASoC: Add json-schema documentation for sound-name-prefix
Date: Wed, 8 Sep 2021 06:59:32 -0500 [thread overview]
Message-ID: <YTilpGuVKifYfGTY@robh.at.kernel.org> (raw)
In-Reply-To: <1630686919-19495-2-git-send-email-spujar@nvidia.com>
On Fri, 03 Sep 2021 22:05:17 +0530, Sameer Pujar wrote:
> The 'sound-name-prefix' is used to prepend suitable strings to a
> component widgets or controls. This is helpful when there are
> multiple instances of the same component. Add relevant json-schema
> and is inspired from sound-name-prefix.txt documentation.
>
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> Cc: Jerome Brunet <jbrunet@baylibre.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Reviewed-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
> .../devicetree/bindings/sound/name-prefix.yaml | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/name-prefix.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-09-08 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 16:35 [PATCH v3 0/3] Convert name-prefix doc to json-schema Sameer Pujar
2021-09-03 16:35 ` [PATCH v3 1/3] ASoC: Add json-schema documentation for sound-name-prefix Sameer Pujar
2021-09-08 11:59 ` Rob Herring [this message]
2021-09-03 16:35 ` [PATCH v3 2/3] ASoC: Use schema reference " Sameer Pujar
2021-09-20 12:57 ` Rob Herring
2021-09-21 15:15 ` Sameer Pujar
2021-09-03 16:35 ` [PATCH v3 3/3] ASoC: Remove name-prefix.txt Sameer Pujar
2021-09-08 11:59 ` Rob Herring
2021-09-13 10:53 ` [PATCH v3 0/3] Convert name-prefix doc to json-schema 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=YTilpGuVKifYfGTY@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=spujar@nvidia.com \
--cc=stephan@gerhold.net \
--cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).