linux-kernel - Re: [PATCH v5 0/2] spi: Add support for Realtek RTL838x/RTL839x SoC 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: <161246849215.26351.5239275196969035314.b4-ty@kernel.org>
Date:   Thu, 04 Feb 2021 19:54:52 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Rob Herring <robh+dt@...nel.org>, linux-kernel@...r.kernel.org,
        Birger Koblitz <mail@...ger-koblitz.de>,
        linux-spi@...r.kernel.org, Bert Vermeulen <bert@...t.com>,
        devicetree@...r.kernel.org
Subject: Re: [PATCH v5 0/2] spi: Add support for Realtek RTL838x/RTL839x SoC SPI

On Wed, 20 Jan 2021 14:59:26 +0100, Bert Vermeulen wrote:
> v5:
> - Changed SoC compatible to list exact models
> 
> v4:
> - Added SoC series-specific compatible matches.
> 
> v3:
> - Added cpu_relax() to busy loop.
> - Dropped .remove callback from driver struct.
> - Use (variations of) realtek-rtl as prefix.
> - Dropped Kconfig entry, and use MACH_REALTEK_RTL setting to build the
>   driver, since there's no point booting without the SPI-connected flash.
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: spi: Realtek RTL838x/RTL839x SPI controller
      commit: 6acbd614c2c8d3b8de5fb7605d6e24b9b3a8a17b
[2/2] spi: realtek-rtl: Add support for Realtek RTL838x/RTL839x SPI controllers
      commit: a8af5cc2ff1e804694629a8ef320935629dd15ba

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