[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b736e11e-430a-462b-898a-d5e1dcf7f74a@wanadoo.fr>
Date: Sat, 18 May 2024 10:34:33 +0200
From: Christophe JAILLET <christophe.jaillet@...adoo.fr>
To: Mark Brown <broonie@...nel.org>
Cc: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
cezary.rojewski@...el.com, pierre-louis.bossart@...ux.intel.com,
peter.ujfalusi@...ux.intel.com, yung-chuan.liao@...ux.intel.com,
ranjani.sridharan@...ux.intel.com, kai.vehmanen@...ux.intel.com,
srinivas.kandagatla@...aro.org, bgoswami@...cinc.com, daniel.baluta@....com,
linux-sound@...r.kernel.org, alsa-devel@...a-project.org,
sound-open-firmware@...a-project.org, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 1/6] ASoC: topology: Constify an argument of
snd_soc_tplg_component_load()
Le 14/05/2024 à 12:21, Mark Brown a écrit :
> 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.
Ok.
I usually do, but I thought that the subjects were self-explanatory
enough in this case.
Do you want me to resend?
CJ
Powered by blists - more mailing lists