Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     abbotti@mev.co.uk, linux-spi@vger.kernel.org
Cc:     linux-kernel@vger.kernel.org
In-Reply-To: <20220510115141.212779-1-abbotti@mev.co.uk>
References: <20220510115141.212779-1-abbotti@mev.co.uk>
Subject: Re: [PATCH 0/2] spi: cadence-quadspi: a couple of minor cleanups
Message-Id: <165219418387.389013.6193637410235087757.b4-ty@kernel.org>
Date:   Tue, 10 May 2022 15:49:43 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 10 May 2022 12:51:39 +0100, Ian Abbott wrote:
> Just a couple of trivial source code cleanups.
> 
> Ian Abbott (2):
>   spi: cadence-quadspi: Add missing blank line in
>     cqspi_request_mmap_dma()
>   spi: cadence-quadspi: remove unnecessary (void *) casts
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: cadence-quadspi: Add missing blank line in cqspi_request_mmap_dma()
      commit: 76159e2f9a0fa29fd9fccb262687d95282985b49
[2/2] spi: cadence-quadspi: remove unnecessary (void *) casts
      commit: 0d8688298d6a43f2e187dad1e45871248123764f

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