mbox series

[0/3] spi: spi-fsl-lpspi: Some calculation improvements

Message ID 20240930093056.93418-1-wahrenst@gmx.net
Headers show
Series spi: spi-fsl-lpspi: Some calculation improvements | expand

Message

Stefan Wahren Sept. 30, 2024, 9:30 a.m. UTC 
This series contains some improvements for spi-fsl-lpspi which are
related to the calculations within fsl_lpspi_set_bitrate.

Stefan Wahren (3):
  spi: spi-fsl-lpspi: Adjust type of scldiv
  spi: spi-fsl-lpspi: Fix specifiers in fsl_lpspi_set_bitrate
  spi: spi-fsl-lpspi: support effective_speed_hz

 drivers/spi/spi-fsl-lpspi.c | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

--
2.34.1

Comments

Mark Brown Oct. 1, 2024, 5:46 p.m. UTC | #1 
On Mon, 30 Sep 2024 11:30:53 +0200, Stefan Wahren wrote:
> This series contains some improvements for spi-fsl-lpspi which are
> related to the calculations within fsl_lpspi_set_bitrate.
> 
> Stefan Wahren (3):
>   spi: spi-fsl-lpspi: Adjust type of scldiv
>   spi: spi-fsl-lpspi: Fix specifiers in fsl_lpspi_set_bitrate
>   spi: spi-fsl-lpspi: support effective_speed_hz
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: spi-fsl-lpspi: Adjust type of scldiv
      commit: fa8ecda9876ac1e7b29257aa82af1fd0695496e2
[2/3] spi: spi-fsl-lpspi: Fix specifiers in fsl_lpspi_set_bitrate
      commit: 7086f49dc442837996c08350a4d590e790b499db
[3/3] spi: spi-fsl-lpspi: support effective_speed_hz
      commit: 667b5e803a94f1ce48ac85b3fef94891a8d40ccf

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