[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <159846939971.39744.13669389911848588325.b4-ty@kernel.org>
Date: Wed, 26 Aug 2020 20:16:39 +0100
From: Mark Brown <broonie@...nel.org>
To: Vinod Koul <vkoul@...nel.org>
Cc: Rander Wang <rander.wang@...ux.intel.com>,
alsa-devel@...a-project.org, Naveen Manohar <naveen.m@...el.com>,
Oder Chiou <oder_chiou@...ltek.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
linux-kernel@...r.kernel.org,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Takashi Iwai <tiwai@...e.com>,
Ryan Lee <ryans.lee@...imintegrated.com>,
Shuming Fan <shumingf@...ltek.com>
Subject: Re: [PATCH v2 0/5] ASoC: Fix return check for devm_regmap_init_sdw()
On Wed, 26 Aug 2020 22:03:35 +0530, Vinod Koul wrote:
> This series attempts to fix return check for devm_regmap_init_sdw()
>
> Changes in v2:
> - Add missing patch for rt711
> - Add patch for rt700
>
> Vinod Koul (5):
> ASoC: max98373: Fix return check for devm_regmap_init_sdw()
> ASoC: rt1308-sdw: Fix return check for devm_regmap_init_sdw()
> ASoC: rt711: Fix return check for devm_regmap_init_sdw()
> ASoC: rt715: Fix return check for devm_regmap_init_sdw()
> ASoC: rt700: Fix return check for devm_regmap_init_sdw()
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/5] ASoC: max98373: Fix return check for devm_regmap_init_sdw()
commit: 6e0c9b5f90978287b5a3d38ee83203d295f375f1
[2/5] ASoC: rt1308-sdw: Fix return check for devm_regmap_init_sdw()
commit: 344850d93c098e1b17e6f89d5e436893e9762ef3
[3/5] ASoC: rt711: Fix return check for devm_regmap_init_sdw()
commit: be1a4b2c56db860a220c6f74d461188e5733264a
[4/5] ASoC: rt715: Fix return check for devm_regmap_init_sdw()
commit: 282eb0b52e3f0399ee48a4cad0d9ffec840b0164
[5/5] ASoC: rt700: Fix return check for devm_regmap_init_sdw()
commit: db1a4250aef53775ec0094b81454213319cc8c74
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