From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
broonie@kernel.org, srinivas.kandagatla@linaro.org,
jank@cadence.com, slawomir.blauciak@intel.com,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH v3 0/4] soundwire: debugfs support for 5.4
Date: Fri, 23 Aug 2019 10:34:58 -0500 [thread overview]
Message-ID: <cbf39078-1ef2-f05b-e2d7-b4695299e56b@linux.intel.com> (raw)
In-Reply-To: <20190823063404.GB2672@vkoul-mobl>
On 8/23/19 1:34 AM, Vinod Koul wrote:
> 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
Thanks for the edit, appreciate not having to resend a series.
prev parent reply other threads:[~2019-08-23 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 18:58 [PATCH v3 0/4] soundwire: debugfs support for 5.4 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 ` [PATCH v3 0/4] soundwire: debugfs support for 5.4 Vinod Koul
2019-08-23 15:34 ` Pierre-Louis Bossart [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=cbf39078-1ef2-f05b-e2d7-b4695299e56b@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--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=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=vkoul@kernel.org \
--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 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.