From: Joe Perches <joe@perches.com>
To: Mark Brown <broonie@kernel.org>, Wang Qing <wangqing@vivo.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound/soc/codecs: fix spelling typo in comments
Date: Thu, 24 Sep 2020 09:01:21 -0700 [thread overview]
Message-ID: <062568971307793dcc80337f85545c4765241933.camel@perches.com> (raw)
In-Reply-To: <20200924123346.GE4754@sirena.org.uk>
On Thu, 2020-09-24 at 13:33 +0100, Mark Brown wrote:
> On Thu, Sep 24, 2020 at 02:43:59PM +0800, Wang Qing wrote:
> > Modify the comment typo: "compliment" -> "complement".
>
> These are both English words,
with rather different meanings.
> and compliment appears to be the one that
> is used in the datasheet for this part...
It's difficult to fix datasheet typos.
next prev parent reply other threads:[~2020-09-24 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 6:43 [PATCH] sound/soc/codecs: fix spelling typo in comments Wang Qing
2020-09-24 12:33 ` Mark Brown
2020-09-24 16:01 ` Joe Perches [this message]
2020-09-24 16:12 ` Mark Brown
2020-09-24 16:22 ` Joe Perches
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=062568971307793dcc80337f85545c4765241933.camel@perches.com \
--to=joe@perches.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=wangqing@vivo.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).