From: Mark Brown <broonie@kernel.org>
To: "Colin King (gmail)" <colin.i.king@gmail.com>
Cc: Kiseok Jo <kiseok.jo@irondevice.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] ASoC: codec: sma1307: replace spelling mistake with new error message
Date: Fri, 8 Aug 2025 13:10:24 +0100 [thread overview]
Message-ID: <91c874a0-5897-4019-ac35-e34187382061@sirena.org.uk> (raw)
In-Reply-To: <bb06d3bf-684b-4479-8b86-72aed622e453@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On Fri, Aug 08, 2025 at 12:35:40PM +0100, Colin King (gmail) wrote:
> On 08/08/2025 12:30, Mark Brown wrote:
> > On Fri, Aug 08, 2025 at 11:53:24AM +0100, Colin Ian King wrote:
> > > - dev_err(sma1307->dev, "%s: failed by dismatch \"%s\"\n",
> > > + dev_err(sma1307->dev, "%s: checksum failed \"%s\"\n",
> > It's definitely an unusual term and the reword makes sense but that does
> > make sense to me as a word, I don't think it's a spelling error as such.
> "Dismatch" is not a standard English word. It's likely a misspelling of
> "mismatch" or a neologism formed by adding the prefix "dis-" to "match". I
> understand it a niche term, I just think it is preferable not to use it for
> folk who's first language isn't English.
My comment was specifically that it doesn't look like a spelling
mistake.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-08-08 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 10:53 Colin Ian King
2025-08-08 11:30 ` Mark Brown
2025-08-08 11:35 ` Colin King (gmail)
2025-08-08 12:10 ` Mark Brown [this message]
2025-08-12 11:05 ` 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=91c874a0-5897-4019-ac35-e34187382061@sirena.org.uk \
--to=broonie@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kiseok.jo@irondevice.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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®