From: Markus Elfring <Markus.Elfring@web.de>
To: Venkata Prasad Potturu <venkataprasad.potturu@amd.com>,
linux-sound@vger.kernel.org, alsa-devel@alsa-project.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"Basavaraj Hiregoudar" <Basavaraj.Hiregoudar@amd.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Mark Brown" <broonie@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Sunil-kumar Dommati" <Sunil-kumar.Dommati@amd.com>,
"Syed Saba Kareem" <Syed.SabaKareem@amd.com>,
"Takashi Iwai" <tiwai@suse.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Vijendar Mukunda" <Vijendar.Mukunda@amd.com>
Subject: Re: [PATCH 1/3] ASoC: amd: acp: Fix NULL pointer deref on acp resume path
Date: Fri, 25 Apr 2025 10:55:16 +0200 [thread overview]
Message-ID: <6f4ee1e8-aa28-4d20-96bc-b2a7343ddbcc@web.de> (raw)
In-Reply-To: <20250425060144.1773265-1-venkataprasad.potturu@amd.com>
> update chip data using dev_get_drvdata(dev->parent) instead of
> dev_get_platdata(dev).
…
* Would you get into the mood to replace the text “deref” in the summary phrase?
* Can a cover letter usually be helpful for such a patch series?
Regards,
Markus
next prev parent reply other threads:[~2025-04-25 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 6:01 [PATCH 1/3] ASoC: amd: acp: Fix NULL pointer deref on acp resume path Venkata Prasad Potturu
2025-04-25 6:01 ` [PATCH 2/3] ASoC: amd: acp: Fix NULL pointer deref in acp_i2s_set_tdm_slot Venkata Prasad Potturu
2025-04-25 6:01 ` [PATCH 3/3] ASoC: amd: acp: Fix devm_snd_soc_register_card(acp-pdm-mach) failure Venkata Prasad Potturu
2025-04-25 8:55 ` Markus Elfring [this message]
2025-04-25 9:05 ` [PATCH 1/3] ASoC: amd: acp: Fix NULL pointer deref on acp resume path Greg Kroah-Hartman
2025-04-25 11:30 ` Mark Brown
2025-04-25 17:40 ` Mark Brown
2025-05-01 22:16 ` Niklas Schnelle
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=6f4ee1e8-aa28-4d20-96bc-b2a7343ddbcc@web.de \
--to=markus.elfring@web.de \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Syed.SabaKareem@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perex@perex.cz \
--cc=peterz@infradead.org \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=venkataprasad.potturu@amd.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.