All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: alsa-devel@alsa-project.org, kai.vehmanen@linux.intel.com,
	pierre-louis.bossart@linux.intel.com,
	ranjani.sridharan@linux.intel.com,
	amadeuszx.slawinski@linux.intel.com, cujomalainey@chromium.org,
	yung-chuan.liao@linux.intel.com
Subject: Re: [PATCH v2 0/3] ASoC: SOF: Fixes for suspend after firmware crash
Date: Tue, 27 Dec 2022 00:14:55 +0000	[thread overview]
Message-ID: <167210009543.553759.6276339953213630705.b4-ty@kernel.org> (raw)
In-Reply-To: <20221220125629.8469-1-peter.ujfalusi@linux.intel.com>

On Tue, 20 Dec 2022 14:56:26 +0200, Peter Ujfalusi wrote:
> This is the followup series for the v1 sent out by Ranjani [1]. Unfortunately
> Ranjani was dragged away to another issue and could not send the update herself.
> 
> Changes since v1:
> - In patch 2, move the tear_down_all_pipelines call instead of duplicating it
> 
> Amadeusz: I have kept the check as it is:
> if (tplg_ops && tplg_ops->tear_down_all_pipelines)
> I'm preparing the ops optionality change series which would require this change.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/3] ASoC: SOF: pm: Set target state earlier
      commit: 6f95eec6fb89e195dbdf30de65553c7fc57d9372
[2/3] ASoC: SOF: pm: Always tear down pipelines before DSP suspend
      commit: d185e0689abc98ef55fb7a7d75aa0c48a0ed5838
[3/3] ASoC: SOF: Add FW state to debugfs
      commit: 9a9134fd56f6ba614ff7b2b3b0bac0bf1d0dc0c9

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

  parent reply	other threads:[~2022-12-27  0:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 12:56 [PATCH v2 0/3] ASoC: SOF: Fixes for suspend after firmware crash Peter Ujfalusi
2022-12-20 12:56 ` [PATCH v2 1/3] ASoC: SOF: pm: Set target state earlier Peter Ujfalusi
2022-12-20 12:56 ` [PATCH v2 2/3] ASoC: SOF: pm: Always tear down pipelines before DSP suspend Peter Ujfalusi
2022-12-20 12:56 ` [PATCH v2 3/3] ASoC: SOF: Add FW state to debugfs Peter Ujfalusi
2022-12-27  0:14 ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-20 12:56 [PATCH v2 0/3] ASoC: SOF: Fixes for suspend after firmware crash Peter Ujfalusi

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=167210009543.553759.6276339953213630705.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=cujomalainey@chromium.org \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=peter.ujfalusi@linux.intel.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.