linux-kernel - Re: [PATCH v5 0/6] spi: Adding support for Microchip Sparx5 SoC

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: <159958565716.16771.6460929787549553831.b4-ty@kernel.org>
Date:   Tue, 08 Sep 2020 18:20:57 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Peter Rosin <peda@...ntia.se>,
        Lars Povlsen <lars.povlsen@...rochip.com>
Cc:     linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Microchip Linux Driver Support <UNGLinuxDriver@...rochip.com>,
        Serge Semin <fancer.lancer@...il.com>,
        Serge Semin <Sergey.Semin@...kalelectronics.ru>,
        linux-spi@...r.kernel.org
Subject: Re: [PATCH v5 0/6] spi: Adding support for Microchip Sparx5 SoC

On Mon, 24 Aug 2020 22:30:04 +0200, Lars Povlsen wrote:
> The series add support for the Sparx5 SoC SPI controller in the
> spi-dw-mmio.c spi driver.
> 
> v5 changes:
> - rx-sample-delay-ns documentation changes from Rob Herring:
>  - Drop superfluous type $ref
>  - Add default value = 0
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: dw: Add support for RX sample delay register
      commit: bac70b54ecb53b3d5af862dd4fcbaaad8f34ed23
[2/3] spi: dw: Add Microchip Sparx5 support
      commit: 53a09635ce56e3041fb3cbc7ceef8f5de28259a5
[3/3] dt-bindings: snps, dw-apb-ssi: Add sparx5 support, plus rx-sample-delay-ns property
      commit: 5ce78f4456a9b2cb103f5bad9e62636e8d086152

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