linux-kernel - Re: [PATCH v1 1/4] ASoC: Intel: bytcht_es8316: Get platform data via dev_get

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu,  7 Oct 2021 22:37:25 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Cc:     Mark Brown <broonie@...nel.org>,
        Jie Yang <yang.jie@...ux.intel.com>,
        Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Cezary Rojewski <cezary.rojewski@...el.com>,
        Takashi Iwai <tiwai@...e.com>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Subject: Re: [PATCH v1 1/4] ASoC: Intel: bytcht_es8316: Get platform data via dev_get_platdata()

On Wed, 6 Oct 2021 18:04:25 +0300, Andy Shevchenko wrote:
> Access to platform data via dev_get_platdata() getter to make code cleaner.
> 
> 

Applied to

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

Thanks!

[1/4] ASoC: Intel: bytcht_es8316: Get platform data via dev_get_platdata()
      commit: 2577b868a48ef3601116908738efbe570451e605
[2/4] ASoC: Intel: bytcht_es8316: Use temporary variable for struct device
      commit: 6f32c521061b704c0198be3ba9834f5a64ea5605
[3/4] ASoC: Intel: bytcht_es8316: Switch to use gpiod_get_optional()
      commit: 10f4a96543b744c8cc7ef8b0799af21d911dd37d
[4/4] ASoC: Intel: bytcht_es8316: Utilize dev_err_probe() to avoid log saturation
      commit: c25d4546ca452b2e8c03bc735e4c65bc6dd751dd

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