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 X-Spam-Level: X-Spam-Status: No, score=-9.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6B3AFC433DF for ; Mon, 10 Aug 2020 18:58:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 495AC221E2 for ; Mon, 10 Aug 2020 18:58:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1597085924; bh=24U7VqkQ+pHnnq6Bw4WtCe+NRWb+V7m3I56c0o8d7bk=; h=Date:From:To:Cc:In-Reply-To:References:Subject:List-ID:From; b=lDaLYRvvOOHU7UZWgVCqmMoAmcACLxdE/Y6RjfuNyMyRzDbXBOthNOpnl3Goc4H58 5aK6ab5lwtUIjDvvxOWx2vAGgiWHsPSxvytKtQgpInFkVgPgjQHyYHiXsJmjKxk7Xe 7bUNrdt9pfnbA+YuxxlCkR3iY3hF3jUDhzd0lcx4= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728306AbgHJS6n (ORCPT ); Mon, 10 Aug 2020 14:58:43 -0400 Received: from mail.kernel.org ([198.145.29.99]:54282 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728071AbgHJS6m (ORCPT ); Mon, 10 Aug 2020 14:58:42 -0400 Received: from localhost (fw-tnat.cambridge.arm.com [217.140.96.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6604120774; Mon, 10 Aug 2020 18:58:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1597085921; bh=24U7VqkQ+pHnnq6Bw4WtCe+NRWb+V7m3I56c0o8d7bk=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=JYLRru3ojJbQ8xF0AaEov1jm87ZY8B6yICkfUwSLpMIaBVeLpqeW45krSd4yeLP2c aOWU34+15Ag1eWjRzxAC31bKtHTRV0COAN6Odi65SYJchR5IGKWpmkUJMu5MP3L6II xZK9cklpg0S7MtGbNFtoSnUjOox4/MGEY2lIDAVs= Date: Mon, 10 Aug 2020 19:58:15 +0100 From: Mark Brown To: Alain Volmat , amelie.delaunay@st.com Cc: linux-kernel@vger.kernel.org, fabrice.gasnier@st.com, alexandre.torgue@st.com, mcoquelin.stm32@gmail.com, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org In-Reply-To: <1597043558-29668-1-git-send-email-alain.volmat@st.com> References: <1597043558-29668-1-git-send-email-alain.volmat@st.com> Subject: Re: [PATCH v2 0/5] spi: stm32: various driver fixes Message-Id: <159708588098.21609.2579059133743645332.b4-ty@kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 10 Aug 2020 09:12:33 +0200, Alain Volmat wrote: > This serie is a reduced version of the serie > [spi: stm32: various driver enhancements] previously sent. > > Alain Volmat (1): > spi: stm32: always perform registers configuration prior to transfer > > Amelie Delaunay (3): > spi: stm32: fix fifo threshold level in case of short transfer > spi: stm32: fix stm32_spi_prepare_mbr in case of odd clk_rate > spi: stm32: fixes suspend/resume management > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/5] spi: stm32h7: fix race condition at end of transfer commit: 135dd873d3c76d812ae64c668adef3f2c59ed27f [2/5] spi: stm32: fix fifo threshold level in case of short transfer commit: 3373e9004acc0603242622b4378c64bc01d21b5f [3/5] spi: stm32: fix stm32_spi_prepare_mbr in case of odd clk_rate commit: 9cc61973bf9385b19ff5dda4a2a7e265fcba85e4 [4/5] spi: stm32: fixes suspend/resume management commit: db96bf976a4fc65439be0b4524c0d41427d98814 [5/5] spi: stm32: always perform registers configuration prior to transfer commit: 60ccb3515fc61a0124c70aa37317f75b67560024 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