From: Mark Brown <broonie@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
cezary.rojewski@intel.com, pierre-louis.bossart@linux.intel.com,
peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
srinivas.kandagatla@linaro.org, bgoswami@quicinc.com,
daniel.baluta@nxp.com, linux-sound@vger.kernel.org,
alsa-devel@alsa-project.org,
sound-open-firmware@alsa-project.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/6] ASoC: topology: Constify an argument of snd_soc_tplg_component_load()
Date: Tue, 14 May 2024 11:21:38 +0100 [thread overview]
Message-ID: <1fb69d24-03af-4742-9f44-5a93704f5cfb@sirena.org.uk> (raw)
In-Reply-To: <f2f983e791d7f941a95556bb147f426a345d84d4.1715526069.git.christophe.jaillet@wanadoo.fr>
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
On Mon, May 13, 2024 at 07:37:20PM +0200, Christophe JAILLET wrote:
> snd_soc_tplg_component_load() does not modify its "*ops" argument. It
> only read some values and stores it in "soc_tplg.ops".
As mentioned in submitting-patches.rst when submitting a patch series
you should supply a cover letter for that patch series which describes
the overall content of the series. This helps people understand what
they are looking at and how things fit together.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-05-14 10:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 17:37 [PATCH 1/6] ASoC: topology: Constify an argument of snd_soc_tplg_component_load() Christophe JAILLET
2024-05-13 17:37 ` [PATCH 2/6] ASoC: Intel: avs: Constify struct snd_soc_tplg_ops Christophe JAILLET
2024-05-14 7:24 ` Amadeusz Sławiński
2024-05-13 17:37 ` [PATCH 3/6] ASoC: qdsp6: audioreach: " Christophe JAILLET
2024-05-13 17:37 ` [PATCH 4/6] ASoC: Intel: Skylake: " Christophe JAILLET
2024-05-14 7:24 ` Amadeusz Sławiński
2024-05-13 17:37 ` [PATCH 5/6] ASoC: SOF: topology: " Christophe JAILLET
2024-05-13 17:37 ` [PATCH 6/6] const_structs.checkpatch: add snd_soc_tplg_ops Christophe JAILLET
2024-05-14 7:23 ` [PATCH 1/6] ASoC: topology: Constify an argument of snd_soc_tplg_component_load() Amadeusz Sławiński
2024-05-14 10:21 ` Mark Brown [this message]
2024-05-18 8:34 ` Christophe JAILLET
2024-05-20 13:24 ` Mark Brown
2024-05-20 21:31 ` 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=1fb69d24-03af-4742-9f44-5a93704f5cfb@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@quicinc.com \
--cc=cezary.rojewski@intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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).