From: Mark Brown <broonie@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org, vinod.koul@linaro.org,
tiwai@suse.de, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, ranjani.sridharan@linux.intel.com,
hui.wang@canonical.com, vkoul@kernel.org,
srinivas.kandagatla@linaro.org, jank@cadence.com,
mengdong.lin@intel.com, sanyog.r.kale@intel.com,
rander.wang@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH v4 1/3] ASoC: codecs: soundwire: remove port_ready[] usage from codecs.
Date: Tue, 1 Sep 2020 14:51:01 +0100 [thread overview]
Message-ID: <20200901135101.GE6262@sirena.org.uk> (raw)
In-Reply-To: <20200831134318.11443-2-yung-chuan.liao@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
On Mon, Aug 31, 2020 at 09:43:16PM +0800, Bard Liao wrote:
> From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>
> port_ready will be changed to a fixed array in sdw.h and all initialization
> work will be done at soundwire side in the following patch. So remove them
> from codec drivers.
Acked-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-01 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 13:43 [PATCH v4 0/3] ASoC: soundwire: fix port_ready[] dynamic allocation Bard Liao
2020-08-31 13:43 ` [PATCH v4 1/3] ASoC: codecs: soundwire: remove port_ready[] usage from codecs Bard Liao
2020-09-01 13:51 ` Mark Brown [this message]
2020-08-31 13:43 ` [PATCH v4 2/3] soundwire: add definition for maximum number of ports Bard Liao
2020-08-31 13:43 ` [PATCH v4 3/3] soundwire: fix port_ready[] dynamic allocation in mipi_disco Bard Liao
2020-09-03 10:32 ` [PATCH v4 0/3] ASoC: soundwire: fix port_ready[] dynamic allocation 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=20200901135101.GE6262@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--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=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vinod.koul@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox