lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162446397757.55213.13647791401168219427.b4-ty@kernel.org>
Date:   Wed, 23 Jun 2021 17:08:58 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Yang Yingliang <yangyingliang@...wei.com>,
        linux-tegra@...r.kernel.org, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org
Cc:     Mark Brown <broonie@...nel.org>, lgirdwood@...il.com
Subject: Re: [PATCH -next 0/4] ASoC: tegra: Use devm_platform_get_and_ioremap_resource()

On Fri, 18 Jun 2021 10:47:18 +0800, Yang Yingliang wrote:
> Use devm_platform_get_and_ioremap_resource() to simplify
> code.
> 
> Yang Yingliang (4):
>   ASoC: tegra20: i2s: Use devm_platform_get_and_ioremap_resource()
>   ASoC: tegra20: spdif: Use devm_platform_get_and_ioremap_resource()
>   ASoC: tegra: tegra210_admaif: Use
>     devm_platform_get_and_ioremap_resource()
>   ASoC: tegra30: ahub: Use devm_platform_get_and_ioremap_resource()
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: tegra20: i2s: Use devm_platform_get_and_ioremap_resource()
      commit: 8ad9e5baa90f76c5125b23419fc458e206371bce
[2/4] ASoC: tegra20: spdif: Use devm_platform_get_and_ioremap_resource()
      commit: 8d81f0da47bbea7f4eb6cdae5210c8c3bd8ce50f
[3/4] ASoC: tegra: tegra210_admaif: Use devm_platform_get_and_ioremap_resource()
      commit: c29b6382d23c8bea604033f98604b7b1e543b1e7
[4/4] ASoC: tegra30: ahub: Use devm_platform_get_and_ioremap_resource()
      commit: fc8344e63e595fa1f2e783aaae0253570cd8eea8

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ