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:     mail@conchuod.ie, palmer@dabbelt.com, palmer@rivosinc.com,
        lgirdwood@gmail.com, thierry.reding@gmail.com,
        fancer.lancer@gmail.com, daniel.lezcano@linaro.org,
        krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
        daniel@ffwll.ch, sam@ravnborg.org, vkoul@kernel.org,
        airlied@linux.ie, Eugeniy.Paltsev@synopsys.com
Cc:     conor.dooley@microchip.com, paul.walmsley@sifive.com,
        linux-riscv@lists.infradead.org, linux-spi@vger.kernel.org,
        niklas.cassel@wdc.com, linux-kernel@vger.kernel.org,
        damien.lemoal@opensource.wdc.com, dmaengine@vger.kernel.org,
        aou@eecs.berkeley.edu, joabreu@synopsys.com, tglx@linutronix.de,
        dillon.minfei@gmail.com, alsa-devel@alsa-project.org,
        geert@linux-m68k.org, devicetree@vger.kernel.org,
        dri-devel@lists.freedesktop.org, masahiroy@kernel.org
In-Reply-To: <20220629184343.3438856-1-mail@conchuod.ie>
References: <20220629184343.3438856-1-mail@conchuod.ie>
Subject: Re: (subset) [PATCH v3 00/15] Canaan devicetree fixes
Message-Id: <165667147407.1756128.12037224598634241859.b4-ty@kernel.org>
Date:   Fri, 01 Jul 2022 11:31:14 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 29 Jun 2022 19:43:29 +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
> 
> Hey all,
> This series should rid us of dtbs_check errors for the RISC-V Canaan k210
> based boards. To make keeping it that way a little easier, I changed the
> Canaan devicetree Makefile so that it would build all of the devicetrees
> in the directory if SOC_CANAAN.
> 
> [...]

Applied to

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

Thanks!

[04/15] spi: dt-bindings: dw-apb-ssi: update spi-{r,t}x-bus-width
        commit: 8b037cabc4966b010c44a76e05a43d276318bc49

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