From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org
Subject: Re: [PATCH 0/4] ASoC / soc/qcom: Constify APR/GPR callback response data
Date: Tue, 2 Dec 2025 17:08:24 +0000 [thread overview]
Message-ID: <3eef7aee-a3b2-481d-9aa2-262d717970ad@sirena.org.uk> (raw)
In-Reply-To: <20251130-asoc-apr-const-v1-0-d0833f3ed423@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
On Sun, Nov 30, 2025 at 10:40:22AM +0100, Krzysztof Kozlowski wrote:
> Patch #1 and #3 touches also Qualcomm SoC file, so this could go either
> via Qualcomm SoC tree (with Mark's Ack) or via ASoC tree (with Bjorn's
> Ack).
>
> I propose to take it via ASoC tree (Bjorn's Ack), because I am
> constifying things there already, so less possible conflicts.
That works for me, Bjorn?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-12-02 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-30 9:40 Krzysztof Kozlowski
2025-11-30 9:40 ` [PATCH 1/4] ASoC: qcom: Constify APR " Krzysztof Kozlowski
2025-11-30 9:40 ` [PATCH 2/4] soc: qcom: apr: Use typedef for GPR callback member Krzysztof Kozlowski
2025-12-19 20:43 ` Bjorn Andersson
2025-11-30 9:40 ` [PATCH 3/4] ASoC: qcom: Constify GPR callback response data Krzysztof Kozlowski
2025-11-30 9:40 ` [PATCH 4/4] ASoC: qcom: Constify APR/GPR result structs Krzysztof Kozlowski
2025-12-01 15:31 ` [PATCH 0/4] ASoC / soc/qcom: Constify APR/GPR callback response data Srinivas Kandagatla
2025-12-02 17:08 ` Mark Brown [this message]
2025-12-22 20:58 ` Mark Brown
2025-12-23 17:06 ` 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=3eef7aee-a3b2-481d-9aa2-262d717970ad@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzysztof.kozlowski@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=perex@perex.cz \
--cc=srini@kernel.org \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®