From: Sameer Pujar <spujar@nvidia.com>
To: Rob Herring <robh@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: <devicetree@vger.kernel.org>, <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Lubomir Rintel <lkundrak@v3.sk>
Subject: Re: [PATCH 4/4] ASoC: dt-bindings: Refine 'frame-master' and 'bitclock-master' type
Date: Wed, 18 Nov 2020 11:16:33 +0530 [thread overview]
Message-ID: <569d30e4-48ba-51b1-39f3-0edba303873b@nvidia.com> (raw)
In-Reply-To: <20201117013349.2458416-5-robh@kernel.org>
> 'frame-master' and 'bitclock-master' are only a single phandle, so use
> the more specific 'phandle' type definition instead.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> .../devicetree/bindings/sound/audio-graph-port.yaml | 6 ++----
> Documentation/devicetree/bindings/sound/simple-card.yaml | 6 ++----
> 2 files changed, 4 insertions(+), 8 deletions(-)
>
Acked-by: Sameer Pujar <spujar@nvidia.com>
WARNING: multiple messages have this Message-ID (diff)
From: Sameer Pujar <spujar@nvidia.com>
To: Rob Herring <robh@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
Liam Girdwood <lgirdwood@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Lubomir Rintel <lkundrak@v3.sk>
Subject: Re: [PATCH 4/4] ASoC: dt-bindings: Refine 'frame-master' and 'bitclock-master' type
Date: Wed, 18 Nov 2020 11:16:33 +0530 [thread overview]
Message-ID: <569d30e4-48ba-51b1-39f3-0edba303873b@nvidia.com> (raw)
In-Reply-To: <20201117013349.2458416-5-robh@kernel.org>
> 'frame-master' and 'bitclock-master' are only a single phandle, so use
> the more specific 'phandle' type definition instead.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> .../devicetree/bindings/sound/audio-graph-port.yaml | 6 ++----
> Documentation/devicetree/bindings/sound/simple-card.yaml | 6 ++----
> 2 files changed, 4 insertions(+), 8 deletions(-)
>
Acked-by: Sameer Pujar <spujar@nvidia.com>
next prev parent reply other threads:[~2020-11-18 5:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 1:33 [PATCH 0/4] ASoC: graph card schema rework Rob Herring
2020-11-17 1:33 ` Rob Herring
2020-11-17 1:33 ` [PATCH 1/4] ASoC: audio-graph-card: Refactor schema Rob Herring
2020-11-17 1:33 ` Rob Herring
2020-11-18 5:44 ` Sameer Pujar
2020-11-18 5:44 ` Sameer Pujar
2020-11-17 1:33 ` [PATCH 2/4] ASoC: dt-bindings: Use OF graph schema Rob Herring
2020-11-17 1:33 ` Rob Herring
2020-11-17 22:22 ` Rob Herring
2020-11-17 22:22 ` Rob Herring
2020-12-01 7:45 ` Sameer Pujar
2020-12-01 7:45 ` Sameer Pujar
2020-11-17 1:33 ` [PATCH 3/4] ASoC: dt-bindings: marvell,mmp-sspa: Use audio-graph-port schema Rob Herring
2020-11-17 1:33 ` [PATCH 3/4] ASoC: dt-bindings: marvell, mmp-sspa: " Rob Herring
2020-11-18 6:38 ` [PATCH 3/4] ASoC: dt-bindings: marvell,mmp-sspa: " Lubomir Rintel
2020-11-18 6:38 ` Lubomir Rintel
2020-11-17 1:33 ` [PATCH 4/4] ASoC: dt-bindings: Refine 'frame-master' and 'bitclock-master' type Rob Herring
2020-11-17 1:33 ` Rob Herring
2020-11-18 5:46 ` Sameer Pujar [this message]
2020-11-18 5:46 ` Sameer Pujar
2020-11-18 20:59 ` [PATCH 0/4] ASoC: graph card schema rework Mark Brown
2020-11-18 20:59 ` 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=569d30e4-48ba-51b1-39f3-0edba303873b@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=lkundrak@v3.sk \
--cc=robh@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 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.