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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id BAB1EC5478C for ; Mon, 26 Feb 2024 19:17:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Date:Message-Id:Subject: References:In-Reply-To:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=lZhPtmh7BLVUSZDo9b4629TTQ8Z5oCasNt0sIwo9Orw=; b=3KculD93E34RRS yO5UwEowSR6cat6EKzTec2kqQ3Bo6haLV5u857P0b6t9/4S3g0BHtnGwADD4F6NZGB8GT+h/v+EY1 xOJ+BjfyjeU9mXof24qRWDgU0SBGOk7NKtT+FxWBcI8yC4+KPWhjzHOjde6qnKoOhxZf5dXEZ2pYK RvO9unb9pipNpzhjpvY1sGMcA7NWjFhfMJsOuNOfyskrkK2JSp/rzYtGDYTw+cXConPLKPaJHuCIK lA0PF98p+UqJ/hSbuxh+yLKuF2mR9Kb6Yzgdw2xGmxAQiAwvDolP0Z6r5c/SuvhD3LfbEEPIy/Gpg G1hJHEk/4qlA/aWawuAg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1regSs-00000002LWN-2imI; Mon, 26 Feb 2024 19:16:38 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1regSo-00000002LVD-37Kk for linux-arm-kernel@lists.infradead.org; Mon, 26 Feb 2024 19:16:36 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 1D6A7612EA; Mon, 26 Feb 2024 19:16:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D0D98C433F1; Mon, 26 Feb 2024 19:16:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1708974993; bh=SbNCXSNgmsHvZE9a2LpECzn1pLI8U+O6zKu8IEb7FC0=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=MIsnQmVDw/trVh09qDNojxvjYpsL03Abgycr+6i8gxKHJQ2+p7hYTIkhhGt+zGdxZ GX5Pal9Wugiq54uqjJuPA+s+XvZc4zKK8WN9kr+BSzta3JBokdfEiOFEjw5Cl+v9OU vXsBMXBarSnIvdFeGpgCRj3pgIXW3/WXBF+OGELbRJvRzzgBED4xFg/wTKPmfDDlEP Y7kjz8B9/n6PYRs4xUVhaMrliNQcA5/n9rn7f7+T+s4BusEFOFiOlZXyipdARz/SdZ DZsTIWpdTuL1dviT0qsVPKNV4Mg2qcM1I9a3MzhqGkjOPHcWVqq/ltyn8mPr7xtaNC xvvXJ1cDcT8Zw== From: Mark Brown To: David Lechner Cc: Martin Sperl , David Jander , Jonathan Cameron , Michael Hennerich , =?utf-8?q?Nuno_S=C3=A1?= , Alain Volmat , Maxime Coquelin , Alexandre Torgue , linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org, Julien Stephan , Jonathan Cameron In-Reply-To: <20240219-mainline-spi-precook-message-v2-0-4a762c6701b9@baylibre.com> References: <20240219-mainline-spi-precook-message-v2-0-4a762c6701b9@baylibre.com> Subject: Re: (subset) [PATCH v2 0/5] spi: add support for pre-cooking messages Message-Id: <170897499057.117217.2960696908311224436.b4-ty@kernel.org> Date: Mon, 26 Feb 2024 19:16:30 +0000 MIME-Version: 1.0 X-Mailer: b4 0.13-dev-a684c X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240226_111634_867634_8B3977E5 X-CRM114-Status: GOOD ( 13.33 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, 19 Feb 2024 16:33:17 -0600, David Lechner wrote: > This is a follow-up to [1] where it was suggested to break down the > proposed SPI offload support into smaller series. > > This takes on the first suggested task of introducing an API to > "pre-cook" SPI messages. This idea was first discussed extensively in > 2013 [2][3] and revisited more briefly 2022 [4]. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/5] spi: add spi_optimize_message() APIs commit: 7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02 [2/5] spi: move splitting transfers to spi_optimize_message() commit: fab53fea21a909e4e0656764a8ee7c356fe89d6f [3/5] spi: stm32: move splitting transfers to optimize_message commit: c2bcfe7c6edf418d5adf731a7d60a8abd81e952f [4/5] spi: axi-spi-engine: move message compile to optimize_message commit: 7dba2adb063bcf7a293eacb88980e0975b1fb1fd 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 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel