All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Cc: tiwai@suse.de
Subject: Re: [PATCH 0/3] ASoC: SOF: Fixes for suspend after firmware crash
Date: Tue, 27 Dec 2022 00:14:54 +0000	[thread overview]
Message-ID: <167210009423.553759.17739795224754159406.b4-ty@kernel.org> (raw)
In-Reply-To: <20221215185347.1457541-1-ranjani.sridharan@linux.intel.com>

On Thu, 15 Dec 2022 10:53:44 -0800, Ranjani Sridharan wrote:
> This series contains 2 patches to fix device suspend after a firmware
> crash and another patch to allow reading the FW state from debugfs.
> 
> Curtis Malainey (1):
>   ASoC: SOF: Add FW state to debugfs
> 
> Ranjani Sridharan (2):
>   ASoC: SOF: pm: Set target state earlier
>   ASoC: SOF: pm: Always tear down pipelines before DSP suspend
> 
> [...]

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:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 18:53 [PATCH 0/3] ASoC: SOF: Fixes for suspend after firmware crash Ranjani Sridharan
2022-12-15 18:53 ` [PATCH 1/3] ASoC: SOF: pm: Set target state earlier Ranjani Sridharan
2022-12-15 18:53 ` [PATCH 2/3] ASoC: SOF: pm: Always tear down pipelines before DSP suspend Ranjani Sridharan
2022-12-16  9:06   ` Amadeusz Sławiński
2022-12-16 12:50     ` Péter Ujfalusi
2022-12-15 18:53 ` [PATCH 3/3] ASoC: SOF: Add FW state to debugfs Ranjani Sridharan
2022-12-27  0:14 ` Mark Brown [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=167210009423.553759.17739795224754159406.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tiwai@suse.de \
    /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.