linux-kernel - Re: [PATCH v3 0/2] Introduce Socionext F

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]

Date:   Thu, 24 Nov 2022 13:27:03 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>
Cc:     linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        linux-spi@...r.kernel.org
Subject: Re: [PATCH v3 0/2] Introduce Socionext F_OSPI SPI flash controller

On Thu, 24 Nov 2022 09:33:49 +0900, Kunihiko Hayashi wrote:
> This series adds dt-bindings and a driver for Socionext F_OSPI controller
> for connecting an SPI Flash memory over up to 8-bit wide bus.
> The controller supports up to 4 chip selects.
> 
> Changes since v2:
> - Drop a redundant word in the subject line
> - Drop quotes of referenceing URL in dt-bindings
> - Add Reviewed-by line to dt-bindings patch
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: spi: Add Socionext F_OSPI controller
      commit: bcd58c8ca0f89fe6a890f909916bc97561341a06
[2/2] spi: Add Socionext F_OSPI SPI flash controller driver
      commit: 1b74dd64c8612619e399e5a31da79a3636914495

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