From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zhang Yi <zhangyi@everest-semi.com>,
broonie@kernel.org, robh@kernel.org, tiwai@suse.com,
devicetree@vger.kernel.org, conor+dt@kernel.org,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, perex@perex.cz, krzk+dt@kernel.org
Cc: amadeuszx.slawinski@linux.intel.com
Subject: Re: [RESEND v5 2/2] ASoC: dt-bindings: Add Everest ES8389 audio CODEC
Date: Thu, 27 Mar 2025 08:06:44 +0100 [thread overview]
Message-ID: <1023814e-1cc5-4f0d-9d60-cbe848d69a9b@kernel.org> (raw)
In-Reply-To: <20250327063531.47005-3-zhangyi@everest-semi.com>
On 27/03/2025 07:35, Zhang Yi wrote:
> Add device tree binding documentation for Everest ES8389 which
> is different from ES8388
>
> Signed-off-by: Zhang Yi <zhangyi@everest-semi.com>
So you not only ignored review but I gave you long instruction what to
do, so that will not happen. And what happened? You wrote:
"Thank you for the explanation.I will do it in a following patch"
and then ignored it entirely!
That entire instruction was on purpose - to prevent possible mistake, to
explain how the process works, because I assume you will not read our
documents like submitting-patches. Well, you should read them prior to
sending, but it happens, so thus my instruction.
And yet we are in the same spot.
I am not doing the same work twice.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-27 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 6:35 [RESEND v5 0/2] ASoC: codecs: add support for ES8389 Zhang Yi
2025-03-27 6:35 ` [RESEND v5 1/2] " Zhang Yi
2025-03-27 6:35 ` [RESEND v5 2/2] ASoC: dt-bindings: Add Everest ES8389 audio CODEC Zhang Yi
2025-03-27 7:06 ` Krzysztof Kozlowski [this message]
2025-03-27 7:03 ` [RESEND v5 0/2] ASoC: codecs: add support for ES8389 Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2025-03-27 7:21 Zhang Yi
2025-03-27 7:21 ` [RESEND v5 2/2] ASoC: dt-bindings: Add Everest ES8389 audio CODEC Zhang Yi
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=1023814e-1cc5-4f0d-9d60-cbe848d69a9b@kernel.org \
--to=krzk@kernel.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=tiwai@suse.com \
--cc=zhangyi@everest-semi.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