From: Mark Brown <broonie@kernel.org>
To: Md Shofiqul Islam <shofiqtest@gmail.com>
Cc: linux-sound@vger.kernel.org, lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: nau8825: Fix typos in comments
Date: Wed, 6 May 2026 08:34:52 +0900 [thread overview]
Message-ID: <afp-nAp_cRWMWA30@sirena.co.uk> (raw)
In-Reply-To: <20260505221958.3751-1-shofiqtest@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
On Wed, May 06, 2026 at 01:19:58AM +0300, Md Shofiqul Islam wrote:
> Fix spelling mistakes in comments:
> - suppresstion -> suppression (twice)
> - funciton -> function (twice)
> - imedance -> impedance
> - tak -> talk
> ---
> sound/soc/codecs/nau8825.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
You've not provided a Signed-off-by for this so I can't do anything with
it, please see Documentation/process/submitting-patches.rst for details
on what this is and why it's important.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-05-05 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 22:19 [PATCH] ASoC: nau8825: Fix typos in comments Md Shofiqul Islam
2026-05-05 23:34 ` Mark Brown [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=afp-nAp_cRWMWA30@sirena.co.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=shofiqtest@gmail.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