From: Thierry Reding <thierry.reding@gmail.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, Sameer Pujar <spujar@nvidia.com>,
kernel-janitors@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mark Brown <broonie@kernel.org>,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] ASoC: tegra: Fix spelling mistake "fliter" -> "filter"
Date: Tue, 8 Nov 2022 15:22:57 +0100 [thread overview]
Message-ID: <Y2pmQdxMIHl+vgIj@orome> (raw)
In-Reply-To: <20221108111340.115387-1-colin.i.king@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
On Tue, Nov 08, 2022 at 11:13:40AM +0000, Colin Ian King wrote:
> There is a spelling mistake in struct member fliter_structure.
> Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> sound/soc/tegra/tegra210_mbdrc.c | 4 ++--
> sound/soc/tegra/tegra210_mbdrc.h | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
I sometimes wonder how these come to be since it's an obvious typo yet
people manage to make them at least twice. Auto-completion I suspect
might play a role. Anyway, good catch:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Sameer Pujar <spujar@nvidia.com>,
alsa-devel@alsa-project.org, linux-tegra@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: tegra: Fix spelling mistake "fliter" -> "filter"
Date: Tue, 8 Nov 2022 15:22:57 +0100 [thread overview]
Message-ID: <Y2pmQdxMIHl+vgIj@orome> (raw)
In-Reply-To: <20221108111340.115387-1-colin.i.king@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
On Tue, Nov 08, 2022 at 11:13:40AM +0000, Colin Ian King wrote:
> There is a spelling mistake in struct member fliter_structure.
> Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> sound/soc/tegra/tegra210_mbdrc.c | 4 ++--
> sound/soc/tegra/tegra210_mbdrc.h | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
I sometimes wonder how these come to be since it's an obvious typo yet
people manage to make them at least twice. Auto-completion I suspect
might play a role. Anyway, good catch:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-08 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 11:13 [PATCH] ASoC: tegra: Fix spelling mistake "fliter" -> "filter" Colin Ian King
2022-11-08 14:22 ` Thierry Reding [this message]
2022-11-08 14:22 ` Thierry Reding
2022-11-10 21:36 ` 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=Y2pmQdxMIHl+vgIj@orome \
--to=thierry.reding@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=spujar@nvidia.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 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.