From: Dan Carpenter <dan.carpenter@linaro.org>
To: Niranjan H Y <niranjan.hy@ti.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
ckeepax@opensource.cirrus.com, mstrozek@opensource.cirrus.com,
yung-chuan.liao@linux.intel.com, linux-sound@vger.kernel.org,
lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
cezary.rojewski@intel.com, peter.ujfalusi@linux.intel.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
pierre-louis.bossart@linux.dev, navada@ti.com,
shenghao-ding@ti.com, v-hampiholi@ti.com, baojun.xu@ti.com
Subject: Re: [PATCH v2] ASoC: SDCA: bug fix while parsing mipi-sdca-control-cn-list
Date: Mon, 17 Nov 2025 17:42:14 +0300 [thread overview]
Message-ID: <aRs0RlQLRDZwjlTS@stanley.mountain> (raw)
In-Reply-To: <20251110152646.192-1-niranjan.hy@ti.com>
On Mon, Nov 10, 2025 at 08:56:46PM +0530, Niranjan H Y wrote:
> "struct sdca_control" declares "values" field as integer array.
> But the memory allocated to it is of char array. This causes
> crash for sdca_parse_function API. This patch addresses the
> issue by allocating correct data size.
>
> Signed-off-by: Niranjan H Y <niranjan.hy@ti.com>
> ---
Looks good.
Fixes: 50a479527ef0 ("ASoC: SDCA: Add support for -cn- value properties")
regards,
dan carpenter
prev parent reply other threads:[~2025-11-20 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 15:26 [PATCH v2] ASoC: SDCA: bug fix while parsing mipi-sdca-control-cn-list Niranjan H Y
2025-11-10 16:17 ` Charles Keepax
2025-11-10 23:39 ` Mark Brown
2025-11-17 14:42 ` Dan Carpenter [this message]
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=aRs0RlQLRDZwjlTS@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=mstrozek@opensource.cirrus.com \
--cc=navada@ti.com \
--cc=niranjan.hy@ti.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.com \
--cc=v-hampiholi@ti.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).