Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Sheetal ." <sheetal@nvidia.com>,
	broonie@kernel.org, linux-sound@vger.kernel.org
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	jonathanh@nvidia.com, thierry.reding@gmail.com,
	mkumard@nvidia.com, spujar@nvidia.com
Subject: Re: [PATCH 01/10] dt-bindings: ASoC: Document Tegra264 APE support
Date: Wed, 23 Apr 2025 14:46:58 +0200	[thread overview]
Message-ID: <af965f9a-97c9-4e80-8d28-06532b16e80b@kernel.org> (raw)
In-Reply-To: <20250422072805.501152-2-sheetal@nvidia.com>

On 22/04/2025 09:27, Sheetal . wrote:
> diff --git a/Documentation/devicetree/bindings/sound/nvidia,tegra-audio-graph-card.yaml b/Documentation/devicetree/bindings/sound/nvidia,tegra-audio-graph-card.yaml
> index b4bee466d67a..ee33f056b125 100644
> --- a/Documentation/devicetree/bindings/sound/nvidia,tegra-audio-graph-card.yaml
> +++ b/Documentation/devicetree/bindings/sound/nvidia,tegra-audio-graph-card.yaml
> @@ -21,6 +21,7 @@ allOf:
>  properties:
>    compatible:
>      enum:
> +      - nvidia,tegra264-audio-graph-card
>        - nvidia,tegra210-audio-graph-card
>        - nvidia,tegra186-audio-graph-card
>  
> diff --git a/Documentation/devicetree/bindings/sound/nvidia,tegra186-asrc.yaml b/Documentation/devicetree/bindings/sound/nvidia,tegra186-asrc.yaml
> index e15f387c4c29..26e1ed7ec7a7 100644
> --- a/Documentation/devicetree/bindings/sound/nvidia,tegra186-asrc.yaml
> +++ b/Documentation/devicetree/bindings/sound/nvidia,tegra186-asrc.yaml
> @@ -31,7 +31,9 @@ properties:
>  
>    compatible:
>      oneOf:
> -      - const: nvidia,tegra186-asrc
> +      - enum:
> +          - nvidia,tegra264-asrc
> +          - nvidia,tegra186-asrc
Keep proper order, not random, not reversed.

<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.

You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.

Please kindly resend and include all necessary To/Cc entries.
</form letter>

Best regards,
Krzysztof

  reply	other threads:[~2025-04-23 12:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  7:27 [PATCH 00/10] Add Tegra264 support in AHUB drivers Sheetal .
2025-04-22  7:27 ` [PATCH 01/10] dt-bindings: ASoC: Document Tegra264 APE support Sheetal .
2025-04-23 12:46   ` Krzysztof Kozlowski [this message]
     [not found]     ` <22d4729d-590d-4082-ad02-7d4fdbfd08b6@nvidia.com>
2025-04-24  8:50       ` Krzysztof Kozlowski
2025-04-22  7:27 ` [PATCH 02/10] ASoC: tegra: CIF: Add Tegra264 support Sheetal .
2025-04-22  7:27 ` [PATCH 03/10] ASoC: tegra: ADMAIF: " Sheetal .
2025-04-22  7:27 ` [PATCH 04/10] ASoC: tegra: ASRC: Update ARAM address Sheetal .
2025-04-22  7:28 ` [PATCH 05/10] ASoC: tegra: Update PLL rate for Tegra264 Sheetal .
2025-04-22  7:28 ` [PATCH 06/10] ASoC: tegra: I2S: Add Tegra264 support Sheetal .
2025-04-22  7:28 ` [PATCH 07/10] ASoC: tegra: AMX: " Sheetal .
2025-04-22  7:28 ` [PATCH 08/10] ASoC: tegra: ADX: " Sheetal .
2025-04-22  7:28 ` [PATCH 09/10] ASoC: tegra: AHUB: " Sheetal .
2025-04-22  7:28 ` [PATCH 10/10] ASoC: tegra: Tegra264 support in isomgr_bw Sheetal .

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=af965f9a-97c9-4e80-8d28-06532b16e80b@kernel.org \
    --to=krzk@kernel.org \
    --cc=broonie@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=sheetal@nvidia.com \
    --cc=spujar@nvidia.com \
    --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