linux-kernel - Re: [PATCH] spi: spi-qpic-snand: remove unused 'wlen' member of 'struct qpic_spi

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: <174561561639.278558.2940962492116902835.b4-ty@kernel.org>
Date: Fri, 25 Apr 2025 22:13:36 +0100
From: Mark Brown <broonie@...nel.org>
To: Gabor Juhos <j4g8y7@...il.com>
Cc: Sricharan Ramabadhran <quic_srichara@...cinc.com>, 
 Varadarajan Narayanan <quic_varada@...cinc.com>, 
 Md Sadre Alam <quic_mdalam@...cinc.com>, linux-spi@...r.kernel.org, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: spi-qpic-snand: remove unused 'wlen' member of
 'struct qpic_spi_nand'

On Thu, 24 Apr 2025 20:10:59 +0200, Gabor Juhos wrote:
> The 'wlen' member of the qpic_spi_nand structure is never used in the
> code so remove that.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi-qpic-snand: remove unused 'wlen' member of 'struct qpic_spi_nand'
      commit: 64c05a1d66193b3a40ad1f29c3d8ba5483e4e0dc

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