From: Bard Liao <yung-chuan.liao@linux.intel.com>
To: alsa-devel@alsa-project.org, vkoul@kernel.org
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
pierre-louis.bossart@linux.intel.com, bard.liao@intel.com
Subject: [PATCH v2 0/4] soundwire: better error handling in deferred transfers
Date: Thu, 19 Jan 2023 15:32:07 +0800 [thread overview]
Message-ID: <20230119073211.85979-1-yung-chuan.liao@linux.intel.com> (raw)
This is a generic cleanup series.
v2:
- Remove the "soundwire: stream: uniquify dev_err() logs" patch
Pierre-Louis Bossart (4):
soundwire: stream: use consistent pattern for freeing buffers
soundwire: bus: remove sdw_defer argument in sdw_transfer_defer()
soundwire: cadence: use directly bus sdw_defer structure
soundwire: cadence: further simplify low-level xfer_msg_defer()
callback
drivers/soundwire/bus.c | 12 +++++-------
drivers/soundwire/bus.h | 3 +--
drivers/soundwire/cadence_master.c | 20 ++++++++++----------
drivers/soundwire/cadence_master.h | 5 +----
drivers/soundwire/stream.c | 8 ++++----
include/linux/soundwire/sdw.h | 6 +++---
6 files changed, 24 insertions(+), 30 deletions(-)
--
2.25.1
next reply other threads:[~2023-01-19 7:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 7:32 Bard Liao [this message]
2023-01-19 7:32 ` [PATCH v2 1/4] soundwire: stream: use consistent pattern for freeing buffers Bard Liao
2023-01-19 7:32 ` [PATCH v2 2/4] soundwire: bus: remove sdw_defer argument in sdw_transfer_defer() Bard Liao
2023-01-19 7:32 ` [PATCH v2 3/4] soundwire: cadence: use directly bus sdw_defer structure Bard Liao
2023-01-19 7:32 ` [PATCH v2 4/4] soundwire: cadence: further simplify low-level xfer_msg_defer() callback Bard Liao
2023-01-31 14:32 ` [PATCH v2 0/4] soundwire: better error handling in deferred transfers Vinod Koul
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=20230119073211.85979-1-yung-chuan.liao@linux.intel.com \
--to=yung-chuan.liao@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®