public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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,
	Mark Brown <broonie@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Basavaraj Hiregoudar <Basavaraj.Hiregoudar@amd.com>,
	Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
	Emil Velikov <emil.velikov@collabora.com>,
	Jaroslav Kysela <perex@perex.cz>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mario Limonciello <mario.limonciello@amd.com>,
	Sunil-kumar Dommati <Sunil-kumar.Dommati@amd.com>,
	syed saba kareem <ssabakar@amd.com>,
	Takashi Iwai <tiwai@suse.com>,
	Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Subject: Re: [PATCH] ASoC: amd: acp: Fix for ACP SOF dmic tplg component load failure
Date: Mon, 4 Nov 2024 10:35:23 +0100	[thread overview]
Message-ID: <e1ac11b3-b746-4564-8daa-3527aa13e348@web.de> (raw)
In-Reply-To: <20241104091312.1108299-1-venkataprasad.potturu@amd.com>

…
> As SOF framework assigns dailink->stream name, overriding stream name
> other than link name causes SOF dmic component load failure.
…

Will another imperative wording be helpful for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc5#n94

Regards,
Markus

  reply	other threads:[~2024-11-04  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  9:13 [PATCH] ASoC: amd: acp: Fix for ACP SOF dmic tplg component load failure Venkata Prasad Potturu
2024-11-04  9:35 ` Markus Elfring [this message]
2024-11-04 12:16   ` Mark Brown
2024-11-04 14:22 ` Mario Limonciello
2024-11-04 14:35   ` Mukunda,Vijendar
2024-11-04 14:40     ` Mario Limonciello
2024-11-05 16:38 ` Mark Brown

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=e1ac11b3-b746-4564-8daa-3527aa13e348@web.de \
    --to=markus.elfring@web.de \
    --cc=Basavaraj.Hiregoudar@amd.com \
    --cc=Sunil-kumar.Dommati@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=emil.velikov@collabora.com \
    --cc=krzysztof.kozlowski@linaro.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=ssabakar@amd.com \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox