linux-kernel - Re: [PATCH] spi: tle62x0: Add newline to sysfs attribute output

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: <176183606744.67987.12357488709998439720.b4-ty@kernel.org>
Date: Thu, 30 Oct 2025 14:54:27 +0000
From: Mark Brown <broonie@...nel.org>
To: Zhongqiu Han <zhongqiu.han@....qualcomm.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: tle62x0: Add newline to sysfs attribute output

On Thu, 30 Oct 2025 20:47:55 +0800, Zhongqiu Han wrote:
> Append a newline to the sysfs_emit() output in tle62x0_gpio_show. This
> aligns with common kernel conventions and improves readability for
> userspace tools that expect newline-terminated values.
> 
> 

Applied to

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

Thanks!

[1/1] spi: tle62x0: Add newline to sysfs attribute output
      commit: ecd0de438c1f0ee86cf8f6d5047965a2a181444b

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