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-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        linux-rockchip@lists.infradead.org,
        Tobias Schramm <t.schramm@manjaro.org>,
        linux-spi@vger.kernel.org
Cc:     Mark Brown <broonie@kernel.org>, Heiko Stuebner <heiko@sntech.de>
Subject: Re: [PATCH] spi: rockchip: handle zero length transfers without timing out
Date:   Fri,  3 Sep 2021 16:18:43 +0100
Message-Id: <163068228056.51069.15541338141615688512.b4-ty@kernel.org>
In-Reply-To: <20210827050357.165409-1-t.schramm@manjaro.org>
References: <20210827050357.165409-1-t.schramm@manjaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 27 Aug 2021 07:03:57 +0200, Tobias Schramm wrote:
> Previously zero length transfers submitted to the Rokchip SPI driver would
> time out in the SPI layer. This happens because the SPI peripheral does
> not trigger a transfer completion interrupt for zero length transfers.
> 
> Fix that by completing zero length transfers immediately at start of
> transfer.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: rockchip: handle zero length transfers without timing out
      commit: 5457773ef99f25fcc4b238ac76b68e28273250f4

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