From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: perex@perex.cz, tiwai@suse.com, unixbhaskar@gmail.com,
broonie@kernel.org, mirq-linux@rere.qmqm.pl, lars@metafoo.de,
gustavoars@kernel.org, huawei@kernel.org,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Cc: rdunlap@infradead.org
Subject: [PATCH V3] ALSA: pcm: Fix couple of typos
Date: Thu, 25 Mar 2021 14:36:09 +0530 [thread overview]
Message-ID: <20210325090609.10372-1-unixbhaskar@gmail.com> (raw)
s/unconditonally/unconditionally/
s/succesful/successful/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
Changes from V2:
Takashi pointed out that the patch was not applicable due to some unwanted
stuff get into it. Resending it with the new patch creation.
sound/core/pcm_native.c | 82 ++++++++++++++++++++---------------------
1 file changed, 41 insertions(+), 41 deletions(-)
diff --git a/sound/core/pcm_native.c b/sound/core/pcm_native.c
index 17a85f4815d5..afb670d7fd53 100644
--- a/sound/core/pcm_native.c
+++ b/sound/core/pcm_native.c
@@ -1425,7 +1425,7 @@ static int snd_pcm_do_stop(struct snd_pcm_substream *substream,
substream->ops->trigger(substream, SNDRV_PCM_TRIGGER_STOP);
substream->runtime->stop_operating = true;
}
- return 0; /* unconditonally stop all substreams */
+ return 0; /* unconditionally stop all substreams */
}
static void snd_pcm_post_stop(struct snd_pcm_substream *substream,
@@ -1469,7 +1469,7 @@ EXPORT_SYMBOL(snd_pcm_stop);
* After stopping, the state is changed to SETUP.
* Unlike snd_pcm_stop(), this affects only the given stream.
*
- * Return: Zero if succesful, or a negative error code.
+ * Return: Zero if successful, or a negative error code.
--
2.30.1
next reply other threads:[~2021-03-25 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 9:06 Bhaskar Chowdhury [this message]
2021-03-25 9:37 ` [PATCH V3] ALSA: pcm: Fix couple of typos Takashi Iwai
2021-03-25 9:56 ` Bhaskar Chowdhury
2021-03-25 10:47 ` Takashi Iwai
2021-03-25 12:07 ` Bhaskar Chowdhury
2021-03-25 16:35 ` Randy Dunlap
2021-03-26 6:53 ` Bhaskar Chowdhury
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=20210325090609.10372-1-unixbhaskar@gmail.com \
--to=unixbhaskar@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gustavoars@kernel.org \
--cc=huawei@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=perex@perex.cz \
--cc=rdunlap@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).