linux-kernel - Re: [PATCH -next] ASoC: Intel: skylake: remove unnecessary dev_set

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: <166427485820.60697.7549055145038298678.b4-ty@kernel.org>
Date:   Tue, 27 Sep 2022 11:34:18 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Yang Yingliang <yangyingliang@...wei.com>,
        alsa-devel@...a-project.org
Cc:     tiwai@...e.de, cezary.rojewski@...el.com,
        pierre-louis.bossart@...ux.intel.com
Subject: Re: [PATCH -next] ASoC: Intel: skylake: remove unnecessary dev_set_drvdata()

On Fri, 16 Sep 2022 22:07:57 +0800, Yang Yingliang wrote:
> Remove unnecessary dev_set_drvdata() in skl_remove(), the driver_data
> will be set to NULL in device_unbind_cleanup() after calling ->remove().
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: Intel: skylake: remove unnecessary dev_set_drvdata()
      commit: d508260e89a7d1889bbb5788fdfc52cc3eb8ddb6

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