Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Shenghao Ding <shenghao-ding@ti.com>, Kevin Lu <kevin-lu@ti.com>,
	 Baojun Xu <baojun.xu@ti.com>, Sen Wang <sen@ti.com>,
	 Liam Girdwood <lgirdwood@gmail.com>,
	 Andrey Golovko <andrey.golovko@gmail.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	 Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	 Antoine Monnet <antoine@montane.tech>,
	Pengpeng Hou <pengpeng@iscas.ac.cn>,
	 linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: tas2783-sdw: drop stale regcache on uninitialized re-attach
Date: Fri, 31 Jul 2026 15:55:16 +0100	[thread overview]
Message-ID: <178550971605.353541.7399708585037800981.b4-ty@b4> (raw)
In-Reply-To: <3e2751d1fb027bed0f09c88e5e56da8f@gmail.com>

On Mon, 27 Jul 2026 12:33:09 +0300, Andrey Golovko wrote:
> ASoC: tas2783-sdw: drop stale regcache on uninitialized re-attach

Applied to

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

Thanks!

[1/1] ASoC: tas2783-sdw: drop stale regcache on uninitialized re-attach
      https://git.kernel.org/broonie/sound/c/b627da430357

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:[~2026-07-31 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27  8:35 [PATCH] ASoC: tas2783-sdw: drop stale regcache on uninitialized re-attach Andrey Golovko
2026-07-27  9:06 ` Pierre-Louis Bossart
2026-07-27  9:33 ` [PATCH v2] " Andrey Golovko
2026-07-27 11:59   ` Mark Brown
2026-07-31 14:55   ` 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=178550971605.353541.7399708585037800981.b4-ty@b4 \
    --to=broonie@kernel.org \
    --cc=andrey.golovko@gmail.com \
    --cc=antoine@montane.tech \
    --cc=baojun.xu@ti.com \
    --cc=kevin-lu@ti.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=pengpeng@iscas.ac.cn \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=sen@ti.com \
    --cc=shenghao-ding@ti.com \
    --cc=tiwai@suse.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