Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Mark Brown <broonie@kernel.org>
To:     linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-spi@vger.kernel.org, Dan Sneddon <dan.sneddon@microchip.com>
Cc:     Mark Brown <broonie@kernel.org>,
        Alexandre Belloni <alexandre.belloni@bootlin.com>,
        Tudor Ambarus <tudor.ambarus@microchip.com>,
        Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: Re: [PATCH 1/2] spi: atmel: Switch to transfer_one transfer method
Date:   Thu,  3 Jun 2021 19:41:46 +0100
Message-Id: <162274571327.15050.7169168930168648183.b4-ty@kernel.org>
In-Reply-To: <20210602160816.4890-1-dan.sneddon@microchip.com>
References: <20210602160816.4890-1-dan.sneddon@microchip.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 2 Jun 2021 09:08:14 -0700, Dan Sneddon wrote:
> Switch from using our own transfer_one_message routine to using the one
> provided by the SPI core.

Applied to

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

Thanks!

[1/2] spi: atmel: Switch to transfer_one transfer method
      commit: 5fa5e6dec762305a783e918a90a05369fc10e346
[2/2] spi: atmel: Reduce spin lock usage
      commit: 4abd641501663493764949f045ebf9f8c0da0307

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