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
| ||
|
Date: Wed, 07 Dec 2022 17:37:42 +0000 From: Mark Brown <broonie@...nel.org> To: ye.xingchen@....com.cn Cc: shengjiu.wang@...il.com, xiubo.lee@...il.com, festevam@...il.com, nicoleotsuka@...il.com, lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de, linux-imx@....com, alsa-devel@...a-project.org, linuxppc-dev@...ts.ozlabs.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] ASoC: imx-audmux: use sysfs_emit() to instead of scnprintf() On Mon, 05 Dec 2022 19:43:47 +0800, ye.xingchen@....com.cn wrote: > Follow the advice of the Documentation/filesystems/sysfs.rst and show() > should only use sysfs_emit() or sysfs_emit_at() when formatting the > value to be returned to user space. > > Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: imx-audmux: use sysfs_emit() to instead of scnprintf() commit: a39bc7cf8e284653fb6fd9d897f269f4ac80cf52 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