linux-kernel - Re: [PATCH] spi: f_ospi: Add missing spi_mem_default_supports

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: <167951086286.1093026.17196294862299360106.b4-ty@kernel.org>
Date:   Wed, 22 Mar 2023 18:47:42 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: f_ospi: Add missing spi_mem_default_supports_op()
 helper

On Wed, 22 Mar 2023 11:31:01 +0900, Kunihiko Hayashi wrote:
> The .supports_op() callback function returns true by default after
> performing driver-specific checks. Therefore the driver cannot apply
> the buswidth in devicetree.
> 
> Call spi_mem_default_supports_op() helper to handle the buswidth
> in devicetree.
> 
> [...]

Applied to

   broonie/spi.git for-next

Thanks!

[1/1] spi: f_ospi: Add missing spi_mem_default_supports_op() helper
      commit: bc43c5ec1a97772269785d19f62d32c91ac5fc36

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