From: Mark Brown <broonie@kernel.org>
To: Zhang Yi <zhangyi@everest-semi.com>
Cc: tiwai@suse.com, linux-sound@vger.kernel.org,
peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
ckeepax@opensource.cirrus.com, vkoul@kernel.org
Subject: Re: [PATCH v12 1/6] ASoC: sdw_utils: add soc_sdw_es9356
Date: Sun, 10 May 2026 20:44:44 +0900 [thread overview]
Message-ID: <agBvrGo2H6RG1siz@sirena.co.uk> (raw)
In-Reply-To: <20260509101102.10286-2-zhangyi@everest-semi.com>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
On Sat, May 09, 2026 at 06:10:57PM +0800, Zhang Yi wrote:
> +int asoc_sdw_es9356_init(struct snd_soc_card *card,
> + struct snd_soc_dai_link *dai_links,
> + struct asoc_sdw_codec_info *info,
> + bool playback);
Is this defined somewhere? I don't seem to see it, the changelog
references updates to soc_sdw_es9356 but I don't see it in the diffstat
or the patches.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-05-10 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 10:10 [PATCH v12 0/6] Add es9356 focused SoundWire CODEC Zhang Yi
2026-05-09 10:10 ` [PATCH v12 1/6] ASoC: sdw_utils: add soc_sdw_es9356 Zhang Yi
2026-05-10 11:44 ` Mark Brown [this message]
2026-05-09 10:10 ` [PATCH v12 2/6] ASoC: sdw_utils: add ES9356 in codec_info_list Zhang Yi
2026-05-09 10:10 ` [PATCH v12 3/6] ASoC: es9356-sdca: Add ES9356 SDCA driver Zhang Yi
2026-05-09 10:11 ` [PATCH v12 4/6] ASoC: Intel: soc-acpi: arl: Add es9356 support Zhang Yi
2026-05-09 10:11 ` [PATCH v12 5/6] ASoC: Intel: sof_sdw: add " Zhang Yi
2026-05-09 10:11 ` [PATCH v12 6/6] soundwire: intel_auxdevice: Add es9356 to wake_capable_list Zhang Yi
2026-05-09 11:58 ` [PATCH v12 0/6] Add es9356 focused SoundWire CODEC Pierre-Louis Bossart
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=agBvrGo2H6RG1siz@sirena.co.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.