From: Mark Brown <broonie@kernel.org>
To: shawnguo@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com,
linux-imx@nxp.com, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stefan Moring <stefan.moring@technolution.nl>
Subject: Re: [PATCH] spi: Increase imx51 ecspi burst length based on transfer length
Date: Tue, 11 Jul 2023 23:04:01 +0100 [thread overview]
Message-ID: <168911304110.642798.9300862955272613470.b4-ty@kernel.org> (raw)
In-Reply-To: <20230628125406.237949-1-stefan.moring@technolution.nl>
On Wed, 28 Jun 2023 14:54:06 +0200, Stefan Moring wrote:
> IMX51 supports 4096 bit burst lengths. Using the spi transfer length
> instead of bits_per_word increases performance significantly.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: Increase imx51 ecspi burst length based on transfer length
commit: 15a6af94a2779d5dfb42ee4bfac858ea8e964a3f
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
next prev parent reply other threads:[~2023-07-11 22:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 12:54 Stefan Moring
2023-06-28 13:16 ` Fabio Estevam
2023-06-28 13:20 ` Stefan Moring
2024-06-18 11:58 ` Marc Kleine-Budde
2024-06-18 15:59 ` Marc Kleine-Budde
2024-06-18 16:02 ` Mark Brown
2024-06-18 16:06 ` Marc Kleine-Budde
2024-06-18 16:11 ` Mark Brown
2023-07-11 22:04 ` Mark Brown [this message]
2023-09-14 22:47 ` Sebastian Reichel
[not found] ` <CAB3BuKAEFewb6W5K=Z2ZX9Xx0gA+RW+XKY-Mkn-PfBOfq3eb+A@mail.gmail.com>
2023-09-16 23:53 ` Sebastian Reichel
[not found] <CAB3BuKAVzXWNNiYDceNCpBqBmKyEykKA3rX=cfTyz+gWaJcnkA@mail.gmail.com>
2023-06-28 11:54 ` Mark Brown
2023-06-28 12:55 ` Stefan Moring
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=168911304110.642798.9300862955272613470.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan.moring@technolution.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®