From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mark Brown <broonie@kernel.org>, Seven Lee <wtli@nuvoton.com>
Cc: lgirdwood@gmail.com, alsa-devel@alsa-project.org,
YHCHuang@nuvoton.com, KCHSU0@nuvoton.com, CTLIN0@nuvoton.com,
SJLIN0@nuvoton.com, scott6986@gmail.com,
supercraig0719@gmail.com, dardar923@gmail.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH] ASoC: dt-bindings: nau8821: Convert to dtschema
Date: Thu, 22 Jun 2023 10:33:47 +0200 [thread overview]
Message-ID: <956657b8-bae1-2096-e932-3a1ae6852431@kernel.org> (raw)
In-Reply-To: <99102ee0-ed59-4e60-89d2-60964cec012c@sirena.org.uk>
On 21/06/2023 20:13, Mark Brown wrote:
> On Wed, Jun 21, 2023 at 05:39:03PM +0800, Seven Lee wrote:
>> Convert the NAU8821 audio CODEC bindings to DT schema.
>
> This wasn't sent to the DT list or maintainers, it should be in order to
> ensure they can review it. Copying in the list and leaving the whole
> message for context.
Thanks.
DT list is being used for testing the patches, so this has to be resend
following get_maintainers.pl output.
Seven,
You already got such feedback before, so it's a repeat of same mistake
in the process. Use tools to automate such tasks, so the process is
being followed without need for additional steps.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-22 8:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 9:39 [PATCH] ASoC: dt-bindings: nau8821: Convert to dtschema Seven Lee
2023-06-21 18:13 ` Mark Brown
2023-06-22 8:33 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-26 10:46 Seven Lee
2023-06-27 6:31 ` Krzysztof Kozlowski
2023-07-12 3:12 ` AS50 WTLi
2023-06-28 8:50 Seven Lee
2023-06-28 9:38 ` Rob Herring
2023-06-28 15:44 ` Rob Herring
2023-07-02 20:18 ` Krzysztof Kozlowski
2023-07-12 11:46 ` 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=956657b8-bae1-2096-e932-3a1ae6852431@kernel.org \
--to=krzk@kernel.org \
--cc=CTLIN0@nuvoton.com \
--cc=KCHSU0@nuvoton.com \
--cc=SJLIN0@nuvoton.com \
--cc=YHCHuang@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dardar923@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=scott6986@gmail.com \
--cc=supercraig0719@gmail.com \
--cc=wtli@nuvoton.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