From: Mark Brown <broonie@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Val Packett <val@packett.cool>,
Srinivas Kandagatla <srini@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>,
Bhushan Shah <bhushan.shah@machinesoul.in>,
Luca Weiss <luca.weiss@fairphone.com>,
Antoine Bernard <zalnir@proton.me>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/6] ASoC: qcom: qdsp6: q6afe: fix clk vote response type mismatch
Date: Thu, 7 May 2026 17:23:31 +0900 [thread overview]
Message-ID: <afxMA7CwyvLR8T1O@sirena.co.uk> (raw)
In-Reply-To: <fafc85f2-ede0-47db-9961-f34b2536a93a@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
On Thu, May 07, 2026 at 10:03:29AM +0200, Konrad Dybcio wrote:
> On 5/7/26 4:16 AM, Mark Brown wrote:
> > Nor me, if the mail doesn't end up in my inbox then I'm going to have no
> > idea that it exists. You need to not only write a cover letter, but
> > also send it to the relevant maintainers just like the patches.
> (which the b4 tool will do for you)
> https://b4.docs.kernel.org/
TBH so will git send-email - it's a pretty unusual flow won't do this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-05-07 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260506204142.659778-1-val@packett.cool>
2026-05-06 20:33 ` [PATCH v2 1/6] ASoC: qcom: qdsp6: q6afe: fix clk vote response type mismatch Val Packett
2026-05-07 0:02 ` Mark Brown
2026-05-07 1:46 ` Val Packett
2026-05-07 2:16 ` Mark Brown
2026-05-07 8:03 ` Konrad Dybcio
2026-05-07 8:23 ` Mark Brown [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=afxMA7CwyvLR8T1O@sirena.co.uk \
--to=broonie@kernel.org \
--cc=bhushan.shah@machinesoul.in \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=perex@perex.cz \
--cc=phone-devel@vger.kernel.org \
--cc=srini@kernel.org \
--cc=srinivas.kandagatla@oss.qualcomm.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=val@packett.cool \
--cc=zalnir@proton.me \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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