From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: <broonie@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>,
<alsa-devel@alsa-project.org>, <linux-sound@vger.kernel.org>
Subject: [PATCH v2 0/4] firmware: cs_dsp: Some small coding improvements
Date: Wed, 10 Jul 2024 11:36:36 +0100 [thread overview]
Message-ID: <20240710103640.78197-1-rf@opensource.cirrus.com> (raw)
Commit series that makes some small improvements to code and the
kernel log messages.
---
Changes since V1:
- Replaced commit #3 with one that keeps the wmfw format version
message on its own line instead of merging it into the INFO text
message.
- Commit #4 rebased onto the new #3
Richard Fitzgerald (4):
firmware: cs_dsp: Don't allocate temporary buffer for info text
firmware: cs_dsp: Make wmfw and bin filename arguments const char *
firmware: cs_dsp: Clarify wmfw format version log message
firmware: cs_dsp: Rename fw_ver to wmfw_ver
drivers/firmware/cirrus/cs_dsp.c | 68 +++++++++-----------------
include/linux/firmware/cirrus/cs_dsp.h | 10 ++--
sound/soc/codecs/wm_adsp.c | 2 +-
3 files changed, 29 insertions(+), 51 deletions(-)
--
2.39.2
next reply other threads:[~2024-07-10 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 10:36 Richard Fitzgerald [this message]
2024-07-10 10:36 ` [PATCH v2 1/4] firmware: cs_dsp: Don't allocate temporary buffer for info text Richard Fitzgerald
2024-07-10 10:36 ` [PATCH v2 2/4] firmware: cs_dsp: Make wmfw and bin filename arguments const char * Richard Fitzgerald
2024-07-10 10:36 ` [PATCH v2 3/4] firmware: cs_dsp: Clarify wmfw format version log message Richard Fitzgerald
2024-07-10 10:36 ` [PATCH v2 4/4] firmware: cs_dsp: Rename fw_ver to wmfw_ver Richard Fitzgerald
2024-07-10 12:20 ` [PATCH v2 0/4] firmware: cs_dsp: Some small coding improvements Charles Keepax
2024-07-11 1:10 ` 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=20240710103640.78197-1-rf@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.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 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.