From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zhang Yi <zhangyi@everest-semi.com>
Cc: tiwai@suse.com, robh@kernel.org, conor+dt@kernel.org,
broonie@kernel.org, devicetree@vger.kernel.org,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, perex@perex.cz
Subject: Re: [PATCH v4 1/2] ASoC: codecs: add support for ES8389
Date: Mon, 10 Mar 2025 08:10:04 +0100 [thread overview]
Message-ID: <b5487295-241f-4b6a-9274-4764f42fc36d@kernel.org> (raw)
In-Reply-To: <20250310030357.120390-1-zhangyi@everest-semi.com>
On 10/03/2025 04:03, Zhang Yi wrote:
> I apologize for not responding to this review comment.
> But I did view these review comments and fixed the error.
> In the meantime I will modify my cc list, do I need to resend a new version
> of the patch to correct my error in my cc list?
Why this list uses different addresses in the first place?
None of the patches had changelog, so you put additional effort on us to
actually check what changed (see submitting patches).
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-10 7:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 3:03 [PATCH v4 1/2] ASoC: codecs: add support for ES8389 Zhang Yi
2025-03-10 7:10 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-10 7:43 Zhang Yi
2025-03-07 8:00 Zhang Yi
2025-03-06 7:23 Zhang Yi
2025-03-06 13:24 ` Mark Brown
2025-03-05 9:18 Zhang Yi
2025-03-05 2:56 Zhang Yi
2025-03-05 13:06 ` Mark Brown
2025-03-04 11:47 [PATCH v4 0/2] " Zhang Yi
2025-03-04 11:47 ` [PATCH v4 1/2] " Zhang Yi
2025-03-04 19:08 ` 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=b5487295-241f-4b6a-9274-4764f42fc36d@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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;
as well as URLs for NNTP newsgroup(s).