From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 09D64EB64DD for ; Thu, 15 Jun 2023 13:16:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239479AbjFONQJ (ORCPT ); Thu, 15 Jun 2023 09:16:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35284 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230055AbjFONQH (ORCPT ); Thu, 15 Jun 2023 09:16:07 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B1E4B270C; Thu, 15 Jun 2023 06:16:03 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 4E07260BB1; Thu, 15 Jun 2023 13:16:03 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 79BB8C433C8; Thu, 15 Jun 2023 13:15:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1686834962; bh=BZz7VgE7FZsHyhQC20/TP0fYQCt9kxxbS+7BpFxp0Qg=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=ONIbZw9nFYdVAI8RzqPvNfyDIkAQ1WIVTIL3GcbFQ6BxtBYOxrwysYJuk22+zeGMN Sga/nSXVvexeb2lhSdEwomGBeq6VwBBGKlHopueeoFrWZ15yqzeSIHAi4cNtdTdUxt UwVS7TTNYCQhDUHMTmX8qwX21OdbY2sDggdiUcY+t2Rb8jPFCv/jptT5V+zWN9xWi5 bV6ol0zgnOl0HKUOUBgw0n4mtsQ20IQ8jXwoyIHOuIhwuOhACpr/6UtOp5W/RtDWLo BgGT5FQbzSxJ5em79FWybn+N5Qfm+M2X0c464X6tyrQ1+BMTcyI/37IcCM9S6WbIes dDYoVTAKJmJyg== From: Mark Brown To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Alexandre Torgue , Alain Volmat , Valentin Caron Cc: linux-spi@vger.kernel.org, devicetree@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org In-Reply-To: <20230615075815.310261-1-valentin.caron@foss.st.com> References: <20230615075815.310261-1-valentin.caron@foss.st.com> Subject: Re: [PATCH v3 0/4] spi: stm32: add spi device mode Message-Id: <168683495795.547441.10667645380315680455.b4-ty@kernel.org> Date: Thu, 15 Jun 2023 14:15:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.13-dev-c6835 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 15 Jun 2023 09:58:11 +0200, Valentin Caron wrote: > STM32 SPI can operate in device mode. > This series adds this functionnality in spi-stm32 driver. > > Since v2: > - Rename this series: spi device mode > > Since v1: > - Do not add #address-cells and #size-cells in st,stm32-spi.yaml > - Do not add cs-gpio description in st,stm32-spi.yaml > - Do not add st,spi-slave-underrun property to handle spi slave underrun > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/4] spi: stm32: renaming of spi_master into spi_controller commit: 6f486556abe35f2e6684f95241acbc463342d3eb [2/4] spi: stm32: use dmaengine_terminate_{a}sync instead of _all commit: 4f2b39dc2d14d4fc55d7a3a140ac07eaa761b701 [3/4] dt-bindings: spi: stm32: disable spi-slave property for stm32f4-f7 commit: e6afe03351ac81fbc4f2b93bf3b356f7b662939d [4/4] spi: stm32: introduction of stm32h7 SPI device mode support commit: e40335fcb89acb274d05deffad9225e973278ec9 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