linux-kernel - Re: [PATCH] spi: hisi-kunpeng: Delete the dump interface of data registers in debugfs

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]

Date: Wed, 17 Apr 2024 11:46:08 +0900
From: Mark Brown <broonie@...nel.org>
To: f.fangjian@...wei.com, Devyn Liu <liudingyuan@...wei.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 jonathan.cameron@...wei.com, liuyonglong@...wei.com
Subject: Re: [PATCH] spi: hisi-kunpeng: Delete the dump interface of data
 registers in debugfs

On Tue, 16 Apr 2024 09:58:39 +0800, Devyn Liu wrote:
> Due to the reading of FIFO during the dump of data registers in
> debugfs, if SPI transmission is in progress, it will be affected
> and may result in transmission failure. Therefore, the dump
> interface of data registers in debugfs is removed.
> 
> 

Applied to

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

Thanks!

[1/1] spi: hisi-kunpeng: Delete the dump interface of data registers in debugfs
      commit: 7430764f5a85d30314aeef2d5438dff1fb0b1d68

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