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 04EC7C433FE for ; Wed, 11 May 2022 18:50:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346483AbiEKSuD (ORCPT ); Wed, 11 May 2022 14:50:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34266 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229954AbiEKSuC (ORCPT ); Wed, 11 May 2022 14:50:02 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 837671ACFAC; Wed, 11 May 2022 11:50:00 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id C137360F2F; Wed, 11 May 2022 18:49:59 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B1788C340EE; Wed, 11 May 2022 18:49:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1652294999; bh=1/F7wsDez0z3wrk2Ax/t4Z3pU9oQk4PfJkSQFlB07kQ=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=cDqvRFyyAsMQPyM+khdB7N1GbvetpBwd8gw7x9bIgfAfpQNYRE1n6r/kuH2fdisZg p6jpzPYr30KC6DqpclR9v9tZzG3vbscidCN78WL38Zp/YbYgW9yuhxEIs2nsboIgqQ 3QQiJYl798OmTnUS2DFlN9Q9dDg5IbLRLTf83HeaBWc9XcA3f08TWaM02S4KzVJ6ek wsW2nF2upA4jm84EIDyps12Xb/KmAt4HSQdsiEk4m41cC7Cb92dZG71GNa0L0kfyFv f/S1UTOD3IuHq0s76crG73KqsbLA5u1mEwBb3RQBYFh+VvNaZUbZI3T9I30fLo2uog 0cNAkNhAZ0Ncg== From: Mark Brown To: alexandre.torgue@foss.st.com, patrice.chotard@foss.st.com Cc: linux-stm32@st-md-mailman.stormreply.com, christophe.kerello@foss.st.com, linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org In-Reply-To: <20220511074644.558874-1-patrice.chotard@foss.st.com> References: <20220511074644.558874-1-patrice.chotard@foss.st.com> Subject: Re: [PATCH 0/3] spi: stm32-qspi: flags management fixes Message-Id: <165229499740.364474.10772649163744226308.b4-ty@kernel.org> Date: Wed, 11 May 2022 19:49:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 11 May 2022 09:46:41 +0200, patrice.chotard@foss.st.com wrote: > From: Patrice Chotard > > This series update flags management in the following cases: > - In APM mode, don't take care of TCF and TEF flags > - Always check TCF flag in stm32_qspi_wait_cmd() > - Don't check BUSY flag when sending new command > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/3] spi: stm32-qspi: Fix wait_cmd timeout in APM mode commit: d83d89ea68b4726700fa87b22db075e4217e691c [2/3] spi: stm32-qspi: Always check SR_TCF flags in stm32_qspi_wait_cmd() commit: 0cf8d32600cf5660ee45d421f1b6e3a129ca58b6 [3/3] spi: stm32-qspi: Remove SR_BUSY bit check before sending command commit: ae16cc18f37bcdea7d4ef57a5e526a60b09a1506 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