[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162430055264.9224.8953420856630209073.b4-ty@kernel.org>
Date: Mon, 21 Jun 2021 19:46:04 +0100
From: Mark Brown <broonie@...nel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
srinivas.kandagatla@...aro.org, alsa-devel@...a-project.org
Cc: Mark Brown <broonie@...nel.org>,
open list <linux-kernel@...r.kernel.org>,
Jack Yu <jack.yu@...ltek.com>, Bard Liao <bard.liao@...el.com>,
tiwai@...e.de, gregkh@...uxfoundation.org,
Jaroslav Kysela <perex@...ex.cz>,
Sanyog Kale <sanyog.r.kale@...el.com>,
Oder Chiou <oder_chiou@...ltek.com>,
Bard liao <yung-chuan.liao@...ux.intel.com>,
Péter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
Hui Wang <hui.wang@...onical.com>,
Shuming Fan <shumingf@...ltek.com>, vkoul@...nel.org,
Rander Wang <rander.wang@...ux.intel.com>
Subject: Re: [PATCH 1/5] soundwire: export sdw_update() and sdw_update_no_pm()
On Mon, 14 Jun 2021 13:08:11 -0500, Pierre-Louis Bossart wrote:
> We currently export sdw_read() and sdw_write() but the sdw_update()
> and sdw_update_no_pm() are currently available only to the bus
> code. This was missed in an earlier contribution.
>
> Export both functions so that codec drivers can perform
> read-modify-write operations without duplicating the code.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] soundwire: export sdw_update() and sdw_update_no_pm()
commit: d38ebaf2c88442a830d402fa7805ddbb60c4cd0c
[2/5] ASoC: rt700-sdw: fix race condition on system suspend
commit: 60888ef827e354d7a3611288d86629e5f1824613
[3/5] ASoC: rt711-sdw: fix race condition on system suspend
commit: 18236370a098428d7639686daa36584d0d363c9e
[4/5] ASoC: rt5682-sdw: fix race condition on system suspend
commit: 14f4946d55d335692462f6fa4eb4ace0bf6ad1d9
[5/5] ASoC: rt711-sdca-sdw: fix race condition on system suspend
commit: d2bf75f4f6b277c35eb887859139df7c2d390b87
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
Powered by blists - more mailing lists