From: Vinod Koul <vkoul@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, broonie@kernel.org, gregkh@linuxfoundation.org,
jank@cadence.com, srinivas.kandagatla@linaro.org,
slawomir.blauciak@intel.com,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [PATCH v3 0/4] soundwire: debugfs support for 5.4
Date: Fri, 23 Aug 2019 12:04:04 +0530 [thread overview]
Message-ID: <20190823063404.GB2672@vkoul-mobl> (raw)
In-Reply-To: <20190821185821.12690-1-pierre-louis.bossart@linux.intel.com>
On 21-08-19, 13:58, Pierre-Louis Bossart wrote:
> This patchset enables debugfs support and corrects all the feedback
> provided on an earlier RFC ('soundwire: updates for 5.4')
>
> There is one remaining hard-coded value in intel.c that will need to
> be fixed in a follow-up patchset not specific to debugfs: we need to
> remove hard-coded Intel-specific configurations from cadence_master.c
> (PDI offsets, etc).
Applied all (i did hand edit of patch 4 to resolve dependency), thanks
--
~Vinod
next prev parent reply other threads:[~2019-08-23 6:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 18:58 Pierre-Louis Bossart
2019-08-21 18:58 ` [PATCH v3 1/4] soundwire: add debugfs support Pierre-Louis Bossart
2019-08-21 18:58 ` [PATCH v3 2/4] soundwire: cadence_master: add debugfs register dump Pierre-Louis Bossart
2019-08-21 18:58 ` [PATCH v3 3/4] soundwire: intel: " Pierre-Louis Bossart
2019-08-21 18:58 ` [PATCH v3 4/4] soundwire: intel: handle disabled links Pierre-Louis Bossart
2019-08-23 6:34 ` Vinod Koul [this message]
2019-08-23 15:34 ` [alsa-devel] [PATCH v3 0/4] soundwire: debugfs support for 5.4 Pierre-Louis Bossart
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=20190823063404.GB2672@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.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
all inboxes | Powered by JetHome®