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 45DBAC433F5 for ; Wed, 19 Jan 2022 18:02:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1356592AbiASSCu (ORCPT ); Wed, 19 Jan 2022 13:02:50 -0500 Received: from dfw.source.kernel.org ([139.178.84.217]:60852 "EHLO dfw.source.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1356581AbiASSCt (ORCPT ); Wed, 19 Jan 2022 13:02:49 -0500 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 9EA7D61653; Wed, 19 Jan 2022 18:02:48 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7A488C004E1; Wed, 19 Jan 2022 18:02:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1642615368; bh=2qp8+c0do7iGqMKUDe+RLIbzFyrSKpLK6ZCDMCrZcLA=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=NNkVzgkPeP3vUXAOk2sOK58xpkoXcyIxpyqtLDEywyofTz6mU25vrAKR3PB8MrmwK Itpshs9pW6Mz8DbYYKf2+GcDxGw4Zeo2kjwwtuBqunoxnwQS/atgzo61nXPqCL/nMd 5OW8xsbf3vHeK6QBY3fYb5F0z6MRDzPHfC4l1VlgczN1LPNgrCcF0w+o5f9jOdZMBy 4ygnqOoP93fP4oR0B0kJ0zoKBHkq+kAHuGr9CQr06B8kK1zgY/XIVyxEaUWiX3juUV 2pF1NZRQ40GcLktmNE1kGmXyy1wTKc/pHhT5DZESCHyM+gBrPTHAZW5hFWY1GV4dk9 mt7DHJjipW76w== From: Mark Brown To: patrice.chotard@foss.st.com, Alexandre Torgue Cc: stable@vger.kernel.org, linux-spi@vger.kernel.org, christophe.kerello@foss.st.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-stm32@st-md-mailman.stormreply.com In-Reply-To: <20220117121744.29729-1-patrice.chotard@foss.st.com> References: <20220117121744.29729-1-patrice.chotard@foss.st.com> Subject: Re: [PATCH v3] spi: stm32-qspi: Update spi registering Message-Id: <164261536622.2816943.17525364866114130985.b4-ty@kernel.org> Date: Wed, 19 Jan 2022 18:02:46 +0000 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 Mon, 17 Jan 2022 13:17:44 +0100, patrice.chotard@foss.st.com wrote: > From: Patrice Chotard > > Some device driver need to communicate to qspi device during the remove > process, qspi controller must be functional when spi_unregister_master() > is called. > > To ensure this, replace devm_spi_register_master() by spi_register_master() > and spi_unregister_master() is called directly in .remove callback before > stopping the qspi controller. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-linus Thanks! [1/1] spi: stm32-qspi: Update spi registering commit: e4d63473d3110afd170e6e0e48494d3789d26136 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