linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Bard Liao <yung-chuan.liao@linux.intel.com>,
	alsa-devel@alsa-project.org, vkoul@kernel.org
Cc: pierre-louis.bossart@linux.intel.com, vinod.koul@linaro.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, sanyog.r.kale@intel.com,
	rander.wang@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH v2 0/4] soundwire: Remove sdw stream operations from Intel
Date: Tue, 8 Sep 2020 14:44:57 +0200	[thread overview]
Message-ID: <28bd0f89-3dc5-0bf4-bf2a-dca62fddc507@perex.cz> (raw)
In-Reply-To: <20200903204739.31206-1-yung-chuan.liao@linux.intel.com>

Dne 03. 09. 20 v 22:47 Bard Liao napsal(a):
> Sdw stream operation APIs can be called once per stream. Move these
> operations to dailink ops. The linked series is "ASoC: Add sdw stream
> operations to dailink ops".
> 
> Pierre-Louis Bossart (4):
>   soundwire: stream: fix NULL/IS_ERR confusion
>   soundwire: intel: fix NULL/ERR_PTR confusion
>   soundwire: intel: remove .trigger operation
>   soundwire: intel: remove stream handling from .prepare and .hw_free
> 
>  drivers/soundwire/intel.c  | 60 +++++---------------------------------
>  drivers/soundwire/stream.c |  2 +-
>  2 files changed, 9 insertions(+), 53 deletions(-)
> 

Straight patches. I tested them. For all:

Acked-by: Jaroslav Kysela <perex@perex.cz>

Note: The ASoC part must be merged in sync -
  "[PATCH v3 0/3] ASoC: Add sdw stream operations to dailink ops."

						Jaroslav
-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

      parent reply	other threads:[~2020-09-08 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 20:47 [PATCH v2 0/4] soundwire: Remove sdw stream operations from Intel Bard Liao
2020-09-03 20:47 ` [PATCH v2 1/4] soundwire: stream: fix NULL/IS_ERR confusion Bard Liao
2020-09-03 20:47 ` [PATCH v2 2/4] soundwire: intel: fix NULL/ERR_PTR confusion Bard Liao
2020-09-03 20:47 ` [PATCH v2 3/4] soundwire: intel: remove .trigger operation Bard Liao
2020-09-03 20:47 ` [PATCH v2 4/4] soundwire: intel: remove stream handling from .prepare and .hw_free Bard Liao
2020-09-04  9:21 ` [PATCH v2 0/4] soundwire: Remove sdw stream operations from Intel Vinod Koul
2020-09-08 12:44 ` Jaroslav Kysela [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=28bd0f89-3dc5-0bf4-bf2a-dca62fddc507@perex.cz \
    --to=perex@perex.cz \
    --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=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;
as well as URLs for NNTP newsgroup(s).