All of
 help / color / mirror / Atom feed
From: Mark Brown <>
To: Takashi Iwai <>
Cc: Hans de Goede <>,,
	Pierre-Louis Bossart <>,
	Marek Szyprowski <>
Subject: Re: [PATCH v2 0/2] ASoC DPCM lockdep fixes
Date: Fri, 28 Jan 2022 23:46:47 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 19 Jan 2022 16:52:47 +0100, Takashi Iwai wrote:
> this is the revised patches for addressing ASoC lockdep warnings due
> to the recent DPCM locking refactoring.
> Takashi
> v1->v2:
>   - minor correction in the changelog for nested lock
>   - debugfs removal workaround
> [...]

Applied to for-linus


[1/2] ASoC: soc-pcm: Fix DPCM lockdep warning due to nested stream locks
      commit: 3c75c0ea5da749bd1efebd1387f2e5011b8c7d78
[2/2] ASoC: soc-pcm: Move debugfs removal out of spinlock
      commit: 9f620684c1ef5a002b6622ecc7b5818e81252f48

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.


      parent reply	other threads:[~2022-01-28 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 15:52 [PATCH v2 0/2] ASoC DPCM lockdep fixes Takashi Iwai
2022-01-19 15:52 ` [PATCH v2 1/2] ASoC: soc-pcm: Fix DPCM lockdep warning due to nested stream locks Takashi Iwai
2022-01-19 15:52 ` [PATCH v2 2/2] ASoC: soc-pcm: Move debugfs removal out of spinlock Takashi Iwai
2022-01-28 23:46 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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.