Received-SPF: pass (google.com: domain of linux-kernel+bounces-54871-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, 
 andy.shevchenko@gmail.com
Cc: Vladimir Oltean <olteanv@gmail.com>, Minjie Du <duminjie@vivo.com>
In-Reply-To: <20240204203127.1186621-1-andy.shevchenko@gmail.com>
References: <20240204203127.1186621-1-andy.shevchenko@gmail.com>
Subject: Re: [PATCH v2 0/2] spi: fsl-dspi: A couple of error handling
 improvements
Message-Id: <170722134868.992289.7755960695527262263.b4-ty@kernel.org>
Date: Tue, 06 Feb 2024 12:09:08 +0000
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Sun, 04 Feb 2024 22:29:17 +0200, andy.shevchenko@gmail.com wrote:
> A couple of error handling improvements here:
> - unshadowing error code from dmaengine_slave_config()
> - making error messages uniform
> 
> In v2:
> - split to two patches (Vladimir)
> - improved commit message in the patch 2 (Vladimir)
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: fsl-dspi: Preserve error code returned by dmaengine_slave_config()
      commit: f156743c526281ddcc19511e9073f8c987506913
[2/2] spi: fsl-dspi: Unify error messaging in dspi_request_dma()
      commit: 51b8e79c45d5a42891c6196dcd3f73cbb599940a

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