linux-kernel - Re: [PATCH v2 0/2] spi: spi-qpic-snand: enable 8 bits ECC strength support

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: <175163431628.70446.712797583195740189.b4-ty@kernel.org>
Date: Fri, 04 Jul 2025 14:05:16 +0100
From: Mark Brown <broonie@...nel.org>
To: Manivannan Sadhasivam <mani@...nel.org>, 
 Miquel Raynal <miquel.raynal@...tlin.com>, 
 Richard Weinberger <richard@....at>, Vignesh Raghavendra <vigneshr@...com>, 
 Gabor Juhos <j4g8y7@...il.com>
Cc: Varadarajan Narayanan <quic_varada@...cinc.com>, 
 Md Sadre Alam <quic_mdalam@...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 v2 0/2] spi: spi-qpic-snand: enable 8 bits ECC strength
 support

On Wed, 02 Jul 2025 14:35:22 +0200, Gabor Juhos wrote:
> This small patch set adds support for 8 bits ECC strength, which widens
> the range of the usable SPI NAND chips with the driver.
> 
> The first one is a preparatory patch which adds some defines which
> allows to avoid using magic values, and the second patch implements
> the actual support.
> 
> [...]

Applied to

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

Thanks!

[1/2] mtd: nand: qpic-common: add defines for ECC_MODE values
      commit: 0dc7e656ddd54c3267b7cc18c1ac8ec1297ed02f
[2/2] spi: spi-qpic-snand: add support for 8 bits ECC strength
      commit: 913bf8d50cbd144c87e9660b591781179182ff59

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