linux-kernel - Re: [PATCH v7 0/2] spi-geni-qcom: Add SPI device mode support for GENI based QuPv3

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: <169083820097.564817.14087328403536590412.b4-ty@kernel.org>
Date:   Mon, 31 Jul 2023 22:16:40 +0100
From:   Mark Brown <broonie@...nel.org>
To:     agross@...nel.org, andersson@...nel.org, konrad.dybcio@...aro.org,
        linux-arm-msm@...r.kernel.org, linux-spi@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Praveen Talari <quic_ptalari@...cinc.com>
Cc:     quic_msavaliy@...cinc.com, quic_vtanuku@...cinc.com,
        quic_vnivarth@...cinc.com, quic_arandive@...cinc.com
Subject: Re: [PATCH v7 0/2] spi-geni-qcom: Add SPI device mode support for
 GENI based QuPv3

On Fri, 14 Jul 2023 09:52:01 +0530, Praveen Talari wrote:
> This series adds spi device mode functionality to geni based Qupv3.
> The common header file contains spi slave related registers and masks.
> 
> Praveen Talari (2):
> 

Applied to

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

Thanks!

[1/2] soc: qcom: geni-se: Add SPI Device mode support for GENI based QuPv3
      commit: 59bbe86bb212b618ec2b50434f54bb4cfc704f44
[2/2] spi: spi-geni-qcom: Add SPI Device mode support for GENI based QuPv3
      commit: d7f74cc31a89a45d4c7deaa5f759661a07a183d6

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