From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
daniel.baluta@nxp.com, ranjani.sridharan@linux.intel.com,
lgirdwood@gmail.com, yung-chuan.liao@linux.intel.com
Subject: Re: [PATCH v2 1/3] ASoC: SOF: sof-audio: setup sched widgets during pipeline complete step
Date: Wed, 24 Nov 2021 15:49:01 +0200 (EET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2111241518470.3554566@eliteleevi.tm.intel.com> (raw)
In-Reply-To: <YZ42x4GkTEboP1bi@sirena.org.uk>
Hi,
On Wed, 24 Nov 2021, Mark Brown wrote:
> On Tue, Nov 23, 2021 at 07:16:04PM +0200, Kai Vehmanen wrote:
>
> > Fixes: 5fcdbb2d45df ("ASoC: SOF: Add support for dynamic pipelines")
> > Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>
> This doesn't actually apply as a fix FWIW, I've queued it for -next.
ack, this won't apply on top of for-5.16. The dependencies around the SOF
dynamic pipelines (and related code) are unfortunately rather complicated
with many recent changes. I now sent these on top of for-5.17/65c16dd2942
as baseline.
Given the limited use of dynamic pipelines in current SOF topologies,
we should be good for 5.16 even if these are left out. The Fixes
tags should still be useful for anyone backporting patches to older
kernels.
Br, Kai
next prev parent reply other threads:[~2021-11-24 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 17:16 [PATCH v2 1/3] ASoC: SOF: sof-audio: setup sched widgets during pipeline complete step Kai Vehmanen
2021-11-23 17:16 ` [PATCH v2 2/3] ASoC: SOF: topology: don't use list_for_each_entry_reverse() Kai Vehmanen
2021-11-23 18:08 ` Mark Brown
2021-11-23 17:16 ` [PATCH v2 3/3] ASoC: SOF: handle paused streams during system suspend Kai Vehmanen
2021-11-24 12:57 ` [PATCH v2 1/3] ASoC: SOF: sof-audio: setup sched widgets during pipeline complete step Mark Brown
2021-11-24 13:49 ` Kai Vehmanen [this message]
2021-11-24 17:36 ` Mark Brown
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=alpine.DEB.2.22.394.2111241518470.3554566@eliteleevi.tm.intel.com \
--to=kai.vehmanen@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--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.