From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: vkoul@kernel.org
Cc: sanyog.r.kale@intel.com,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org
Subject: [PATCH 0/4] soundwire: few trival fixes and cleanups.
Date: Thu, 28 Mar 2019 13:41:30 +0000 [thread overview]
Message-ID: <20190328134134.22479-1-srinivas.kandagatla@linaro.org> (raw)
Hi Vinod,
Here are few trivial updates to soundwire which I found while
trying out Qualcomm WCD934x codecs.
Thanks,
Srinivas Kandagatla (4):
soundwire: add module_sdw_driver helper macro
soundwire: cdns: fix check for number of messages
soundwire: bus: check if pm runtime is enabled before calling
soundwire: remove unused struct sdw_bus_conf definition
drivers/soundwire/bus.c | 16 ++++++++++------
drivers/soundwire/cadence_master.c | 2 +-
include/linux/soundwire/sdw.h | 15 ---------------
include/linux/soundwire/sdw_type.h | 11 +++++++++++
4 files changed, 22 insertions(+), 22 deletions(-)
--
2.21.0
next reply other threads:[~2019-03-28 13:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 13:41 Srinivas Kandagatla [this message]
2019-03-28 13:41 ` [PATCH 1/4] soundwire: add module_sdw_driver helper macro Srinivas Kandagatla
2019-03-29 5:38 ` Vinod Koul
2019-03-28 13:41 ` [PATCH 2/4] soundwire: cdns: fix check for number of messages Srinivas Kandagatla
2019-03-28 14:03 ` Pierre-Louis Bossart
2019-03-28 14:58 ` Srinivas Kandagatla
2019-03-29 3:51 ` Sanyog Kale
2019-03-29 5:54 ` Vinod Koul
2019-03-29 10:06 ` Srinivas Kandagatla
2019-03-28 13:41 ` [PATCH 3/4] soundwire: bus: check if pm runtime is enabled before calling Srinivas Kandagatla
2019-03-28 13:55 ` Pierre-Louis Bossart
2019-03-28 14:37 ` Srinivas Kandagatla
2019-03-29 5:58 ` Vinod Koul
2019-03-29 10:02 ` Srinivas Kandagatla
2019-04-05 15:26 ` Ranjani Sridharan
2019-03-28 13:41 ` [PATCH 4/4] soundwire: remove unused struct sdw_bus_conf definition Srinivas Kandagatla
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=20190328134134.22479-1-srinivas.kandagatla@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--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 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.