linux-kernel - Re: (subset) [PATCH 0/7] Support for Marvell modifications for Cadence XSPI

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 27 Dec 2022 11:57:49 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Witold Sadowski <wsadowski@...vell.com>
Cc:     linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, jpawar@...ence.com,
        pthombar@...ence.com, konrad@...ence.com, wbartczak@...vell.com,
        wzmuda@...vell.com
Subject: Re: (subset) [PATCH 0/7] Support for Marvell modifications for Cadence XSPI

On Mon, 19 Dec 2022 06:42:47 -0800, Witold Sadowski wrote:
> This patch series is fixing bugs, and adding support for
> Marvell changes for Cadence XSPI IP.
> It includes:
> - Polling mode support
> - Changes for modebyte handling
> - Busycycles calculations
> - Marvell specific IP changes
> 
> [...]

Applied to

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

Thanks!

[1/7] spi: cadence: Fix busy cycles calculation
      commit: e8bb8f19e73a1e855e54788f8673b9b49e46b5cd

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