From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
sound-open-firmware@alsa-project.org,
alsa-devel@alsa-project.org
Subject: [PATCH 0/3] ASoC: sof: cleanup Kconfig files
Date: Tue, 13 Oct 2020 19:56:30 -0700 [thread overview]
Message-ID: <20201014025633.4879-1-rdunlap@infradead.org> (raw)
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>
Cc: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Cc: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: Daniel Baluta <daniel.baluta@nxp.com>
Cc: sound-open-firmware@alsa-project.org
Cc: alsa-devel@alsa-project.org
Some general editing of sound/soc/sof/ Kconfig files:
[PATCH 1/3] ASoC: sof: imx: fix Kconfig punctuation
[PATCH 2/3] ASoC: sof: intel: fix Kconfig punctuation and wording
[PATCH 3/3] ASoC: sof: Kconfig: fix Kconfig punctuation and wording
sound/soc/sof/Kconfig | 42 +++++++++++------------
sound/soc/sof/imx/Kconfig | 10 ++---
sound/soc/sof/intel/Kconfig | 62 +++++++++++++++++-----------------
3 files changed, 57 insertions(+), 57 deletions(-)
next reply other threads:[~2020-10-14 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 2:56 Randy Dunlap [this message]
2020-10-14 2:56 ` [PATCH 1/3] ASoC: sof: imx: fix Kconfig punctuation Randy Dunlap
2020-10-14 2:56 ` [PATCH 2/3] ASoC: sof: intel: fix Kconfig punctuation and wording Randy Dunlap
2020-10-14 2:56 ` [PATCH 3/3] ASoC: sof: Kconfig: " Randy Dunlap
2020-10-14 14:37 ` [PATCH 0/3] ASoC: sof: cleanup Kconfig files Pierre-Louis Bossart
2020-10-14 16:11 ` Randy Dunlap
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=20201014025633.4879-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
/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).