From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
alsa-devel@alsa-project.org, tiwai@suse.de,
Randy Dunlap <rdunlap@infradead.org>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>
Subject: Re: [PATCH 3/4] ASoC: SOF: Intel: fix Kconfig punctuation and wording
Date: Thu, 12 Nov 2020 15:07:00 +0000 [thread overview]
Message-ID: <20201112150700.GA15030@sirena.org.uk> (raw)
In-Reply-To: <20201111213533.149963-4-pierre-louis.bossart@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
On Wed, Nov 11, 2020 at 03:35:32PM -0600, Pierre-Louis Bossart wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Add periods at the end of sentences in help text.
> Insert a "not" in one place.
> Fix help text indentation.
> Remove a duplicate "Intel(R)" in one place.
This doesn't apply against current code, please check and resend.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-12 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 21:35 [PATCH 0/4] ASoC: SOF: Kconfig corrections Pierre-Louis Bossart
2020-11-11 21:35 ` [PATCH 1/4] ASoC: SOF: imx: fix Kconfig punctuation Pierre-Louis Bossart
2020-11-11 21:35 ` [PATCH 2/4] ASoC: SOF: Kconfig: fix Kconfig punctuation and wording Pierre-Louis Bossart
2020-11-11 21:35 ` [PATCH 3/4] ASoC: SOF: Intel: " Pierre-Louis Bossart
2020-11-12 15:07 ` Mark Brown [this message]
2020-11-11 21:35 ` [PATCH 4/4] ASoC: SOF: Intel: fix Kconfig dependency for SND_INTEL_DSP_CONFIG Pierre-Louis Bossart
2020-11-12 15:12 ` Mark Brown
2020-11-12 19:39 ` [PATCH 0/4] ASoC: SOF: Kconfig corrections 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=20201112150700.GA15030@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=rdunlap@infradead.org \
--cc=tiwai@suse.de \
/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.