From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org, tiwai@suse.de,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
ranjani.sridharan@linux.intel.com, hui.wang@canonical.com,
broonie@kernel.org, srinivas.kandagatla@linaro.org,
jank@cadence.com, mengdong.lin@intel.com,
slawomir.blauciak@intel.com, sanyog.r.kale@intel.com,
rander.wang@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH v2 0/9] soundwire: intel: revisit SHIM programming
Date: Tue, 21 Jul 2020 16:06:42 +0530 [thread overview]
Message-ID: <20200721103642.GL12965@vkoul-mobl> (raw)
In-Reply-To: <20200716150947.22119-1-yung-chuan.liao@linux.intel.com>
On 16-07-20, 23:09, Bard Liao wrote:
> This series does some cleanup, revisits SHIM programming sequences,
> and merges Soundwire interrupt handlers/threads.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2020-07-21 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 15:09 [PATCH v2 0/9] soundwire: intel: revisit SHIM programming Bard Liao
2020-07-16 15:09 ` [PATCH v2 1/9] soundwire: intel: reuse code for wait loops to set/clear bits Bard Liao
2020-07-16 15:09 ` [PATCH v2 2/9] soundwire: intel: revisit SHIM programming sequences Bard Liao
2020-07-16 15:09 ` [PATCH v2 3/9] soundwire: intel: introduce a helper to arm link synchronization Bard Liao
2020-07-16 15:09 ` [PATCH v2 4/9] soundwire: intel: introduce helper for " Bard Liao
2020-07-16 15:09 ` [PATCH v2 5/9] soundwire: intel_init: add implementation of sdw_intel_enable_irq() Bard Liao
2020-07-16 15:09 ` [PATCH v2 6/9] soundwire: intel_init: use EXPORT_SYMBOL_NS Bard Liao
2020-07-16 15:09 ` [PATCH v2 7/9] soundwire: intel/cadence: merge Soundwire interrupt handlers/threads Bard Liao
2020-07-16 15:09 ` [PATCH v2 8/9] soundwire: intel: add wake interrupt support Bard Liao
2020-07-16 15:09 ` [PATCH v2 9/9] Soundwire: intel_init: save Slave(s) _ADR info in sdw_intel_ctx Bard Liao
2020-07-21 10:36 ` Vinod Koul [this message]
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=20200721103642.GL12965@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=slawomir.blauciak@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox