All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org,  Vignesh Raghavendra <vigneshr@ti.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 Steam Lin <stlin2@winbond.com>
Subject: Re: [PATCH] Revert "spi: cadence-qspi: Improve spi memory performance"
Date: Tue, 01 Apr 2025 11:56:50 +0200	[thread overview]
Message-ID: <87ldsktdb1.fsf@bootlin.com> (raw)
In-Reply-To: <01d6ed23-72e4-4c86-8b1e-d7d9fb440c0b@sirena.org.uk> (Mark Brown's message of "Mon, 31 Mar 2025 14:24:19 +0100")

Hi Mark,

On 31/03/2025 at 14:24:19 +01, Mark Brown <broonie@kernel.org> wrote:

> On Fri, Mar 28, 2025 at 06:35:00PM +0100, Miquel Raynal wrote:
>
>> the probing of the DMA controller has been fixed, and the performances are
>> back to normal, so we can safely revert this commit.
>
>> This reverts commit 6e6363dd2f1e5b3e42505606ea494572c81dbb64.
>
> This commit doesn't appear to exist, you seem to mean cce2200dacd6 (spi:
> cadence-qspi: Improve spi memory performance), I fixed it up for that.

Crap, must have catch the one from my own local tree, thanks for fixing.

> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.

I'm curious, maybe this is a semi-automated message, but do you have a
specific style for reverts that deviates from git's?

> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.
>
> Please include human readable descriptions of things like commits and
> issues being discussed in e-mail in your mails, this makes them much
> easier for humans to read especially when they have no internet access.
> I do frequently catch up on my mail on flights or while otherwise
> travelling so this is even more pressing for me than just being about
> making things a bit easier to read.

As per the "This reverts commit <sha>" this is also the standard Git way
to indicate a revert, I kept it as-is.

Thanks,
Miquèl

  reply	other threads:[~2025-04-01  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 17:35 [PATCH] Revert "spi: cadence-qspi: Improve spi memory performance" Miquel Raynal
2025-03-31 13:24 ` Mark Brown
2025-04-01  9:56   ` Miquel Raynal [this message]
2025-04-01  9:59     ` Mark Brown

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=87ldsktdb1.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=stlin2@winbond.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vigneshr@ti.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 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.