From: Julia Lawall <julia.lawall@lip6.fr>
To: Colin King <colin.king@canonical.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>, Vinod Koul <vinod.koul@intel.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: Intel: sst: fix spelling mistake: "allocationf" -> "allocation"
Date: Wed, 10 May 2017 18:06:26 +0800 (SGT) [thread overview]
Message-ID: <alpine.DEB.2.20.1705101805310.20213@hadrien> (raw)
In-Reply-To: <20170510081655.27123-1-colin.king@canonical.com>
On Wed, 10 May 2017, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in dev_err message.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> sound/soc/intel/atom/sst-mfld-platform-pcm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/intel/atom/sst-mfld-platform-pcm.c b/sound/soc/intel/atom/sst-mfld-platform-pcm.c
> index 21cac1c8dd4c..e74119113713 100644
> --- a/sound/soc/intel/atom/sst-mfld-platform-pcm.c
> +++ b/sound/soc/intel/atom/sst-mfld-platform-pcm.c
> @@ -690,7 +690,7 @@ static int sst_pcm_new(struct snd_soc_pcm_runtime *rtd)
> snd_dma_continuous_data(GFP_DMA),
> SST_MIN_BUFFER, SST_MAX_BUFFER);
> if (retval) {
> - dev_err(rtd->dev, "dma buffer allocationf fail\n");
> + dev_err(rtd->dev, "dma buffer allocation fail\n");
Maybe fail -> failure would be nice too? If the message is useful at all.
julia
> return retval;
> }
> }
> --
> 2.11.0
>
>
prev parent reply other threads:[~2017-05-10 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 8:16 Colin King
2017-05-10 10:06 ` Julia Lawall [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=alpine.DEB.2.20.1705101805310.20213@hadrien \
--to=julia.lawall@lip6.fr \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=colin.king@canonical.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=vinod.koul@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
all inboxes | Powered by JetHome®