mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	 Daire McNamara <daire.mcnamara@microchip.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] spi: microchip-core-qspi: Add regular transfers
Date: Tue, 24 Jun 2025 18:33:41 +0100	[thread overview]
Message-ID: <175078642162.219793.16163815657944029556.b4-ty@kernel.org> (raw)
In-Reply-To: <20250620-finer-yoyo-0bcae988a299@spud>

On Fri, 20 Jun 2025 14:28:23 +0100, Conor Dooley wrote:
> Hey,
> 
> This is a v2 of a patchset I sent about this time last year, adding the
> regular transfer_one_message op to the microchip-core-qspi driver. In that
> v1 Mark expressed his dislike for that op, so v2 is using
> prepare/unprepare/transfer_one instead. The unprepare implementation still
> contains the 750 us delay that the driver had back in v1. I've heard a
> suggestion internally as to why this is needed, but it was unsubstantiated,
> so I still have no justification for it. I held off on sending a v2 because
> of a lack of explanation for the delay, but I don't wanna hold off forever
> for something I might never understand.
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: microchip-core-qspi: set min_speed_hz during probe
      commit: 76f03ce1c6f22805ecf689b1f3ecfb56582eddd5
[2/3] spi: microchip-core-qspi: remove unused param from mchp_coreqspi_write_op()
      commit: 75ca45c472dac206df2ebbc1c0f1f9c3bbdace50
[3/3] spi: microchip-core-qspi: Add regular transfers
      commit: 1256eb42db5d1635f4c6da5b1b58db0b53320883

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


      parent reply	other threads:[~2025-06-24 17:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 13:28 Conor Dooley
2025-06-20 13:28 ` [PATCH v2 1/3] spi: microchip-core-qspi: set min_speed_hz during probe Conor Dooley
2025-06-20 13:28 ` [PATCH v2 2/3] spi: microchip-core-qspi: remove unused param from mchp_coreqspi_write_op() Conor Dooley
2025-06-20 13:28 ` [PATCH v2 3/3] spi: microchip-core-qspi: Add regular transfers Conor Dooley
2025-06-24 17:33 ` 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:
  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=175078642162.219793.16163815657944029556.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=daire.mcnamara@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    /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®