From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sameer Pujar <spujar@nvidia.com>,
broonie@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, thierry.reding@gmail.com,
catalin.marinas@arm.com, will@kernel.org, perex@perex.cz,
tiwai@suse.com
Cc: jonathanh@nvidia.com, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/6] ASoC: tegra: Add binding doc for OPE module
Date: Mon, 30 May 2022 08:47:13 +0200 [thread overview]
Message-ID: <f284612d-c511-9a31-3e0a-e4fb1cc77c6e@linaro.org> (raw)
In-Reply-To: <df57de4e-770d-7331-89e5-a2404fb42f96@nvidia.com>
On 30/05/2022 06:21, Sameer Pujar wrote:
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/sound/nvidia,tegra210-mbdrc.yaml
>>> @@ -0,0 +1,47 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/sound/nvidia,tegra210-mbdrc.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Tegra210 MBDRC Device Tree Bindings
>> Previous comments - s/Device Tree Bindings//
>> - still applies. Please do not ignore it.
>
> I did not ignore this. There was a comment from Mark on this earlier (v1) and I did not see further reply from you. I thought you were OK with the way it is. So if you are saying acronym part is OK and just to remove "Device Tree Bindings" I can send a v3 for this.
Yes, acronym is okay. Just remove the "Device Tree Bindings".
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-05-30 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 10:26 [PATCH v2 0/6] OPE support on Tegra210 and later Sameer Pujar
2022-05-27 10:26 ` [PATCH v2 1/6] ASoC: tegra: Add binding doc for OPE module Sameer Pujar
2022-05-29 14:09 ` Krzysztof Kozlowski
2022-05-30 4:21 ` Sameer Pujar
2022-05-30 6:47 ` Krzysztof Kozlowski [this message]
2022-05-27 10:26 ` [PATCH v2 2/6] ASoC: tegra: Add Tegra210 based OPE driver Sameer Pujar
2022-05-27 10:26 ` [PATCH v2 3/6] ASoC: tegra: AHUB routes for OPE module Sameer Pujar
2022-05-27 10:26 ` [PATCH v2 4/6] arm64: defconfig: Build Tegra " Sameer Pujar
2022-05-27 10:26 ` [PATCH v2 5/6] arm64: tegra: Add OPE device on Tegra210 and later Sameer Pujar
2022-05-27 10:26 ` [PATCH v2 6/6] arm64: tegra: Enable OPE on various platforms Sameer Pujar
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=f284612d-c511-9a31-3e0a-e4fb1cc77c6e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.com \
--cc=will@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).