linux-kernel - Re: [PATCH -next] ASoC: tas2781: No need to set device

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]

Message-Id: <168916239302.46574.14475207879403261091.b4-ty@kernel.org>
Date:   Wed, 12 Jul 2023 12:46:33 +0100
From:   Mark Brown <broonie@...nel.org>
To:     perex@...ex.cz, Yang Li <yang.lee@...ux.alibaba.com>
Cc:     tiwai@...e.com, lgirdwood@...il.com, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org, Abaci Robot <abaci@...ux.alibaba.com>
Subject: Re: [PATCH -next] ASoC: tas2781: No need to set device_driver
 owner

On Sun, 25 Jun 2023 09:05:47 +0800, Yang Li wrote:
> Remove .owner field if calls are used which set it automatically.
> 
> to silence the warning:
> ./sound/soc/codecs/tas2781-i2c.c:746:3-8: No need to set .owner here.  The core will do it.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: tas2781: No need to set device_driver owner
      commit: 24e04c94bebc4144f790a21a93d090cf9673acd9

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