From: Randy Dunlap <rdunlap@infradead.org>
To: Syed Saba Kareem <Syed.SabaKareem@amd.com>,
broonie@kernel.org, alsa-devel@alsa-project.org
Cc: Vijendar.Mukunda@amd.com, Basavaraj.Hiregoudar@amd.com,
Sunil-kumar.Dommati@amd.com, Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Julian Braha <julianbraha@gmail.com>,
Lucas Tanure <tanureal@opensource.cirrus.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: amd: fix spelling mistake: "i.e" -> "i.e."
Date: Tue, 30 Aug 2022 11:10:11 -0700 [thread overview]
Message-ID: <dd45cdec-ee8c-b699-2e23-064a866caa04@infradead.org> (raw)
In-Reply-To: <20220830132259.7759-1-Syed.SabaKareem@amd.com>
On 8/30/22 06:22, Syed Saba Kareem wrote:
> From: Syed Saba kareem <Syed.SabaKareem@amd.com>
>
> trivial fix to spelling mistake in Kconfig File.
>
> Reported by : Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Syed Saba Kareem <Syed.SabaKareem@amd.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> sound/soc/amd/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/amd/Kconfig b/sound/soc/amd/Kconfig
> index 68837d42736d..150786279257 100644
> --- a/sound/soc/amd/Kconfig
> +++ b/sound/soc/amd/Kconfig
> @@ -122,7 +122,7 @@ config SND_SOC_AMD_RPL_ACP6x
> tristate "AMD Audio Coprocessor-v6.2 RPL support"
> depends on X86 && PCI
> help
> - This option enables Audio Coprocessor i.e ACP v6.2 support on
> + This option enables Audio Coprocessor i.e. ACP v6.2 support on
> AMD RPL platform. By enabling this flag build will be
> triggered for ACP PCI driver.
> Say m if you have such a device.
--
~Randy
next prev parent reply other threads:[~2022-08-30 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 13:22 Syed Saba Kareem
2022-08-30 18:10 ` Randy Dunlap [this message]
2022-08-30 19:04 ` 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=dd45cdec-ee8c-b699-2e23-064a866caa04@infradead.org \
--to=rdunlap@infradead.org \
--cc=AjitKumar.Pandey@amd.com \
--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=daniel.baluta@nxp.com \
--cc=julianbraha@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tanureal@opensource.cirrus.com \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®