linux-kernel - Re: [PATCH 0/2] spi transfer paramater changes and baud rate calculation

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: <163784742804.3102022.16557507037490210155.b4-ty@kernel.org>
Date:   Thu, 25 Nov 2021 13:37:08 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, Kamal Dasu <kdasu.kdev@...il.com>,
        linux-spi@...r.kernel.org
Cc:     bcm-kernel-feedback-list@...adcom.com, f.fainelli@...il.com,
        yendapally.reddy@...adcom.com
Subject: Re: [PATCH 0/2] spi transfer paramater changes and baud rate calculation

On Wed, 24 Nov 2021 14:33:51 -0500, Kamal Dasu wrote:
> The changes picks either the 27Mhz or 108MhZ system clock for spi transfers
> based user requested transfer speed. Also we set the master controller transfer
> parameter only if they change.
> 
> Kamal Dasu (2):
>   spi: bcm-qspi: choose sysclk setting based on requested speed
>   spi: bcm-qspi: set transfer parameter only if they change
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: bcm-qspi: choose sysclk setting based on requested speed
      commit: c74526f947ab946273939757c72499c0a5b09826
[2/2] spi: bcm-qspi: set transfer parameter only if they change
      commit: e10a6bb5f52de70c7798b720d16632d4042d2552

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