linux-kernel - Re: [PATCH] spi: bcm-qspi: fix SFDP BFPT read by usig mspi read

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: Mon, 22 Jan 2024 22:07:08 +0000
From: Mark Brown <broonie@...nel.org>
To: Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>, 
 Boris Brezillon <bbrezillon@...nel.org>, 
 Kamal Dasu <kamal.dasu@...adcom.com>
Cc: Kamal Dasu <kdasu.kdev@...il.com>, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: bcm-qspi: fix SFDP BFPT read by usig mspi read

On Tue, 09 Jan 2024 16:00:32 -0500, Kamal Dasu wrote:
> SFDP read shall use the mspi reads when using the bcm_qspi_exec_mem_op()
> call. This fixes SFDP parameter page read failures seen with parts that
> now use SFDP protocol to read the basic flash parameter table.
> 
> 

Applied to

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

Thanks!

[1/1] spi: bcm-qspi: fix SFDP BFPT read by usig mspi read
      commit: f9540ac18bb4afd13d3a09275693793cb18d4afb

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