From: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
sharq0406@gmail.com, kuninori.morimoto.gx@renesas.com,
ckeepax@opensource.cirrus.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 2/2] ASoC: mt8173-max98090: use standard callback to set jack
Date: Wed, 20 May 2026 15:34:59 +0000 [thread overview]
Message-ID: <81b15533-3258-48a8-8d5a-0dcec7027254@oss.qualcomm.com> (raw)
In-Reply-To: <5990fbb1-286f-482d-b02a-d0637494f435@sirena.org.uk>
On 5/20/26 1:42 PM, Mark Brown wrote:
> On Wed, May 20, 2026 at 01:29:30PM +0000, Srinivas Kandagatla wrote:
>> use snd_soc_component_set_jack() instead of custom callback to
>> max98090 codec.
>
> This needs to be squashed into the first commit, otherwise the first
> commit will cause a build break.
I had them in opposite order in my local setup, which is why it did not
break the build for me, I can send out a squashed version.
--Srini
next prev parent reply other threads:[~2026-05-20 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 13:29 [PATCH 0/2] ASoC: codecs: max98090: switch to standard set_jack callback Srinivas Kandagatla
2026-05-20 13:29 ` [PATCH 1/2] ASoC: codecs: max98090: use component " Srinivas Kandagatla
2026-05-20 13:29 ` [PATCH 2/2] ASoC: mt8173-max98090: use standard callback to set jack Srinivas Kandagatla
2026-05-20 13:42 ` Mark Brown
2026-05-20 15:34 ` Srinivas Kandagatla [this message]
2026-05-20 15:41 ` Mark Brown
2026-05-20 23:12 ` kernel test robot
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=81b15533-3258-48a8-8d5a-0dcec7027254@oss.qualcomm.com \
--to=srinivas.kandagatla@oss.qualcomm.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=sharq0406@gmail.com \
--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®