From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 399EE20408C; Tue, 4 Mar 2025 12:34:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741091648; cv=none; b=ZI8es/FakR2br/8/X2ytthF3TmrsCQPiP6PtjUMLDWirQMs0xwzuQpPOsp+yNbIKobPKJaBWQSarssvA7qDCaFbs7rTDQs79fMbh6ZpVgGbiGsw5t+qHWH9hNjEQdVW1lWqVKaGd7mqN6599flKpplCNbqR8zqOhtp3jlTlHaaI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741091648; c=relaxed/simple; bh=zTHWmApFgJPW07OqgetEzjrUkVWnD4jFsoH2YVPS7cM=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=nDfqYpIeXr1pHvHgNsFM2XobNwsZFeNgalzB2oK4/unR6x5ceyLnNZDmv2p9LqZUyafkwuNpCl/BCVGIKYTH7sLMVl0jID9aAGErOiFszXBR9mlPtHCK4rOtnQGCNQ4XFLHcTv4dpmQBfYObaloq//a93nnvYJRdwRaWmXVi/hs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Ufl9pv9Z; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Ufl9pv9Z" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9854FC4CEE7; Tue, 4 Mar 2025 12:34:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1741091647; bh=zTHWmApFgJPW07OqgetEzjrUkVWnD4jFsoH2YVPS7cM=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=Ufl9pv9Zvkj2t9gabq44ETpZFsS8ICkeYA5tMCRVXZeumQJUecaFqAF42fcwdeXuy Rpwjan7npCFZfydLy5hoUAb69rKCmbeE2dSKqxe6tXRad6Nkb4jjqkwGjoApiZOXBt GHkVC7Ja/AcwX+xhYtgkdg7csYXFR90iryllzQEx0yZ5cIf9TahMcYkqc+pjKorOVo iH9ZreU0KappLbyeUqFOfMbE1+DGAK5wbxl02GdaNx+czuO/JTvgOx6J8viZuZOpBm Qdp17OexetG315+tecsPG82Mj5TH9aPZ1kLp8VQ+eKgunf0YwrIEMX489l6+y/3zQ3 Ft2aTNHkkaTqw== From: Mark Brown To: linux-spi@vger.kernel.org, Conor Dooley Cc: Conor Dooley , stable@vger.kernel.org, Daire McNamara , linux-kernel@vger.kernel.org In-Reply-To: <20250114-easiness-pregame-d1d2d4b57e7b@spud> References: <20250114-easiness-pregame-d1d2d4b57e7b@spud> Subject: Re: [PATCH] spi: microchip-core: prevent RX overflows when transmit size > FIFO size Message-Id: <174109164637.27220.10404431321397753624.b4-ty@kernel.org> Date: Tue, 04 Mar 2025 12:34:06 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.15-dev-1b0d6 On Tue, 14 Jan 2025 17:13:49 +0000, Conor Dooley wrote: > When the size of a transfer exceeds the size of the FIFO (32 bytes), RX > overflows will be generated and receive data will be corrupted and > warnings will be produced. For example, here's an error generated by a > transfer of 36 bytes: > > spi_master spi0: mchp_corespi_interrupt: RX OVERFLOW: rxlen: 4, txlen: 0 > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: microchip-core: prevent RX overflows when transmit size > FIFO size commit: 91cf42c63f2d8a9c1bcdfe923218e079b32e1a69 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