linux-kernel - Re: (subset) [PATCH v2 0/3] Add FSD SPI support

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: <164677015776.3181837.8136121419686603738.b4-ty@kernel.org>
Date:   Tue, 08 Mar 2022 20:09:17 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-arm-kernel@...ts.infradead.org,
        Alim Akhtar <alim.akhtar@...sung.com>,
        linux-kernel@...r.kernel.org
Cc:     linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org,
        andi@...zian.org, pankaj.dubey@...sung.com,
        linus.walleij@...aro.org, krzysztof.kozlowski@...onical.com,
        linux-spi@...r.kernel.org, robh+dt@...nel.org
Subject: Re: (subset) [PATCH v2 0/3] Add FSD SPI support

On Fri, 21 Jan 2022 00:54:35 +0530, Alim Akhtar wrote:
> Adds support for SPI controller found in Tesla FSD SoC
> 
> -Changes since v1
> * Splited SPI changes from a larger inital patch set
> * Rebased on Krzysztof's latest (v5) SPI schema changes
> * Added tag
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: dt-bindings: samsung: Add fsd spi compatible
      commit: 363d3c51bc5b3243b5b035a1f50d6d994a1b203f
[2/3] spi: s3c64xx: Add spi port configuration for Tesla FSD SoC
      commit: 4ebb15a15799da4954f1d4926fcd3263ea46e417

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