From: Mark Brown <broonie@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Stefan Moring <stefan.moring@technolution.nl>,
Adam Butcher <adam@jessamine.co.uk>,
Benjamin Bigler <benjamin@bigler.one>,
Fabio Estevam <festevam@gmail.com>,
s.hauer@pengutronix.de, linux-kernel@vger.kernel.org,
Stefan Bigler <linux@bigler.io>,
linux-spi@vger.kernel.org,
Thorsten Scherer <T.Scherer@eckelmann.de>,
Clark Wang <xiaoning.wang@nxp.com>,
linux-imx@nxp.com, kernel@pengutronix.de,
Sebastian Reichel <sre@kernel.org>,
shawnguo@kernel.org, Carlos Song <carlos.song@nxp.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] spi: Increase imx51 ecspi burst length based on transfer length
Date: Tue, 18 Jun 2024 17:02:22 +0100 [thread overview]
Message-ID: <cd8d89d3-c304-4eb6-897f-b423e8196ef2@sirena.org.uk> (raw)
In-Reply-To: <20240618-mature-private-peccary-29f0b6-mkl@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
On Tue, Jun 18, 2024 at 05:59:36PM +0200, Marc Kleine-Budde wrote:
> This patch (15a6af94a277 ("spi: Increase imx51 ecspi burst length based
> on transfer length")) is wrong and the 4 fixes on top of it don't
> finally fix it. I can send a series of 5 reverts, or a manually revert
> the burst length calculation to the original value in one patch.
A single revert should be fine and is probably clearer.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-06-18 16:02 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 [this message]
2024-06-18 16:06 ` Marc Kleine-Budde
2024-06-18 16:11 ` Mark Brown
2023-07-11 22:04 ` Mark Brown
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=cd8d89d3-c304-4eb6-897f-b423e8196ef2@sirena.org.uk \
--to=broonie@kernel.org \
--cc=T.Scherer@eckelmann.de \
--cc=adam@jessamine.co.uk \
--cc=benjamin@bigler.one \
--cc=carlos.song@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--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=linux@bigler.io \
--cc=mkl@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=sre@kernel.org \
--cc=stefan.moring@technolution.nl \
--cc=xiaoning.wang@nxp.com \
/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®