linux-kernel - Re: [PATCH] spi: spi-qpic-snand: document the limited bit error reporting capability

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <174887945434.88179.3123674776894271663.b4-ty@kernel.org>
Date: Mon, 02 Jun 2025 16:50:54 +0100
From: Mark Brown <broonie@...nel.org>
To: Miquel Raynal <miquel.raynal@...tlin.com>, 
 Gabor Juhos <j4g8y7@...il.com>
Cc: Md Sadre Alam <quic_mdalam@...cinc.com>, 
 Varadarajan Narayanan <quic_varada@...cinc.com>, 
 Sricharan Ramabadhran <quic_srichara@...cinc.com>, 
 linux-spi@...r.kernel.org, linux-mtd@...ts.infradead.org, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: spi-qpic-snand: document the limited bit error
 reporting capability

On Tue, 27 May 2025 13:08:16 +0200, Gabor Juhos wrote:
> The QPIC hardware is not capable of reporting the exact number of the
> corrected bit errors, it only reports the number of the corrected bytes.
> 
> Document this behaviour in the code, and also issue a warning message
> to inform the user about it.
> 
> No functional changes.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-qpic-snand: document the limited bit error reporting capability
      commit: 57cf46cd1fe351846e1b065ca9546eef66675ecd

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