From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shenghao Ding <shenghao-ding@ti.com>, broonie@kernel.org
Cc: krzysztof.kozlowski@linaro.org, robh+dt@kernel.org,
andriy.shevchenko@linux.intel.com, lgirdwood@gmail.com,
perex@perex.cz, pierre-louis.bossart@linux.intel.com,
13916275206@139.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, liam.r.girdwood@intel.com,
soyer@irl.hu, tiwai@suse.de
Subject: Re: [PATCH v1 3/3] ASoC: dt-bindings: Add tas2563 into yaml
Date: Sat, 9 Dec 2023 14:52:43 +0100 [thread overview]
Message-ID: <bcbcd3a4-803b-4093-a513-79e3ce0d0ef8@kernel.org> (raw)
In-Reply-To: <20231209080742.1290-3-shenghao-ding@ti.com>
On 09/12/2023 09:07, Shenghao Ding wrote:
> Support tas2563.
>
> Signed-off-by: Shenghao Ding <shenghao-ding@ti.com>
> ---
> .../devicetree/bindings/sound/ti,tas2781.yaml | 17 ++++++++++-------
> 1 file changed, 10 insertions(+), 7 deletions(-)
>
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.
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, thus I will skip this patch entirely till you follow
the process allowing the patch to be tested.
Please kindly resend and include all necessary To/Cc entries.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-12-09 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 8:07 [PATCH v1 1/3] ASoC: tas2781: Add tas2563 into header file Shenghao Ding
2023-12-09 8:07 ` [PATCH v1 2/3] ASoC: tas2781: Add tas2563 into driver Shenghao Ding
2023-12-09 8:07 ` [PATCH v1 3/3] ASoC: dt-bindings: Add tas2563 into yaml Shenghao Ding
2023-12-09 8:13 ` Krzysztof Kozlowski
2023-12-09 8:30 ` [EXTERNAL] " Ding, Shenghao
2023-12-09 10:30 ` Krzysztof Kozlowski
2023-12-09 13:52 ` Krzysztof Kozlowski [this message]
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=bcbcd3a4-803b-4093-a513-79e3ce0d0ef8@kernel.org \
--to=krzk@kernel.org \
--cc=13916275206@139.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=shenghao-ding@ti.com \
--cc=soyer@irl.hu \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®