linux-kernel - Re: [PATCH] Use card->dev in replace of the &pdev->dev argument in the dev

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: <172928168210.188041.8550134088626737627.b4-ty@kernel.org>
Date: Fri, 18 Oct 2024 21:01:22 +0100
From: Mark Brown <broonie@...nel.org>
To: peter.ujfalusi@...il.com, Liu Jing <liujing@...s.chinamobile.com>
Cc: jarkko.nikula@...mer.com, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, alsa-devel@...a-project.org, linux-omap@...r.kernel.org, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Use card->dev in replace of the &pdev->dev argument in
 the dev_err function

On Tue, 15 Oct 2024 15:49:38 +0800, Liu Jing wrote:
> Because card->dev = &pdev->dev is already defined in the rx51_soc_probe function,
> and then &pdev->dev is still used.
> 
> 

Applied to

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

Thanks!

[1/1] Use card->dev in replace of the &pdev->dev argument in the dev_err function
      commit: 4d003b81f46737620c7f9194d305617dfdfce8fb

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