All of
 help / color / mirror / Atom feed
From: Mark Brown <>
	 Adam Butcher <>
Subject: Re: [PATCH v3] spi: spi-imx: fix off-by-one in mx51 CPU mode burst length
Date: Tue, 19 Mar 2024 11:47:36 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, 18 Mar 2024 17:50:52 +0000, Adam Butcher wrote:
> c712c05e46c8 ("spi: imx: fix the burst length at DMA mode and CPU mode")
> corrects three cases of setting the ECSPI burst length but erroneously
> leaves the in-range CPU case one bit to big (in that field a value of
> 0 means 1 bit).  The effect was that transmissions that should have been
> 8-bit bytes appeared as 9-bit causing failed communication with SPI
> devices.
> [...]

Applied to for-next


[1/1] spi: spi-imx: fix off-by-one in mx51 CPU mode burst length
      commit: cf6d79a0f5769b5f4d9579ddaf88d2c30b03b873

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.


      reply	other threads:[~2024-03-19 11:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 17:50 [PATCH v3] spi: spi-imx: fix off-by-one in mx51 CPU mode burst length Adam Butcher
2024-03-19 11:47 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.