linux-kernel - Re: (subset) [PATCH v3 0/3] Tegra QUAD SPI combined sequence mode

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: <164676009171.54618.4072327060855634430.b4-ty@kernel.org>
Date:   Tue, 08 Mar 2022 17:21:31 +0000
From:   Mark Brown <broonie@...nel.org>
To:     thierry.reding@...il.com,
        Krishna Yarlagadda <kyarlagadda@...dia.com>,
        linux-tegra@...r.kernel.org, linux-spi@...r.kernel.org,
        ashishsingha@...dia.com, jonathanh@...dia.com
Cc:     ldewangan@...dia.com, robh+dt@...nel.org, skomatineni@...dia.com,
        p.zabel@...gutronix.de, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org
Subject: Re: (subset) [PATCH v3 0/3] Tegra QUAD SPI combined sequence mode

On Mon, 7 Mar 2022 22:25:16 +0530, Krishna Yarlagadda wrote:
> Add ACPI support for Tegra210 QUAD SPI driver
> Support new Tegra194 feature, combined sequence mode.
> Add Tegra234 bindings.
> 
> v3 changes:
> - document runtime pm disabled in ACPI
> - clear cmb register for non combined sequence
> - fixes for errors reported by kernel test robot
> - skip approved patches
> v2 changes:
> - use combined sequence mode as default
> - remove property to switch transfer modes
> - fix compilation warnings
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: tegra210-quad: add acpi support
      commit: 75a1b44a54bd97500e524cf42e8c81cc632672b3
[2/3] spi: tegra210-quad: combined sequence mode
      commit: 1b8342cc4a387933780c50f0cf51c94455be7d11

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