linux-kernel - Re: [PATCH 0/3] spi-bcm-qspi spcr3 enahancements

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: <163397094904.6819.8623150916603608652.b4-ty@kernel.org>
Date:   Mon, 11 Oct 2021 18:01:38 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org, Kamal Dasu <kdasu.kdev@...il.com>,
        linux-kernel@...r.kernel.org
Cc:     Mark Brown <broonie@...nel.org>,
        bcm-kernel-feedback-list@...adcom.com,
        yendapally.reddy@...adcom.com, f.fainelli@...il.com
Subject: Re: [PATCH 0/3] spi-bcm-qspi spcr3 enahancements

On Fri, 8 Oct 2021 16:36:00 -0400, Kamal Dasu wrote:
> This change set feature enahancements for spcr3 transfer modes as well as
> adds support for half-duplex 3-wire mode transfer.
> 
> Kamal Dasu (3):
>   spi: bcm-qspi: Add mspi spcr3 32/64-bits xfer mode
>   spi: bcm-qspi: clear MSPI spifie interrupt during probe
>   spi: bcm-qspi: add support for 3-wire mode for half duplex transfer
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: bcm-qspi: Add mspi spcr3 32/64-bits xfer mode
      commit: ee4d62c47326c69e57180da53c057e55f0e73e35
[2/3] spi: bcm-qspi: clear MSPI spifie interrupt during probe
      commit: 75b3cb97eb1f05042745c0655a7145b0262d4c5c
[3/3] spi: bcm-qspi: add support for 3-wire mode for half duplex transfer
      commit: e81cd07dcf50ef4811f6667dba89c5614278cbdd

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