From:   Mark Brown <broonie@kernel.org>
To:     devicetree@vger.kernel.org, linux-spi@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        William Qiu <william.qiu@starfivetech.com>
Cc:     Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Philipp Zabel <p.zabel@pengutronix.de>,
        Ziv Xu <ziv.xu@starfivetech.com>
In-Reply-To: <20230302105221.197421-1-william.qiu@starfivetech.com>
References: <20230302105221.197421-1-william.qiu@starfivetech.com>
Subject: Re: [PATCH v1 0/2] Add Quad SPI driver for StarFive JH7110 SoC
Message-Id: <167810954467.76172.7217821282766106312.b4-ty@kernel.org>
Date:   Mon, 06 Mar 2023 13:32:24 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Thu, 02 Mar 2023 18:52:19 +0800, William Qiu wrote:
> This patchset adds initial rudimentary support for the StarFive
> Quad SPI controller driver. And this driver will be used in
> StarFive's VisionFive 2 board.The first patch constrain
> minItems/maxItems of resets for JH7110 QSPI and Patch 2 adds
> support for StarFive JH7110 QSPI.
> 
> The patch series is based on v6.2.
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: qspi: cdns,qspi-nor: constrain minItems/maxItems of resets
      commit: 13f1033e07588b7d1151d22d7ee3ca8f16181de7
[2/2] spi: cadence-quadspi: Add support for StarFive JH7110 QSPI
      commit: 47fef94afeae2a125607b6b45145594713471320

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