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=-6.1 required=3.0 tests=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 7335CC433E0 for ; Fri, 19 Jun 2020 13:28:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 446A820DD4 for ; Fri, 19 Jun 2020 13:28:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592573310; bh=woHoEU4qR1vtVDk6B4g7zX0biyS6r/lidqoPWMRgCmo=; h=Date:From:To:Cc:In-Reply-To:References:Subject:List-ID:From; b=buceWI0DtTLp/arRohzaJKrsVdseL7VVMtH7mHHUtYtb5dsA63Qbp08T1ZgoU02yd icplcwRj0J5hmxX2SxoFfzkhAtA/ZaBMXdNfjxTchdZoTGfefZUDLjgWWDhz9mlMNB ByNmEhaDOXlVZtHo41+g/nz/LHPqRW7XHE20cgD4= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728068AbgFSN22 (ORCPT ); Fri, 19 Jun 2020 09:28:28 -0400 Received: from mail.kernel.org ([198.145.29.99]:46346 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732737AbgFSN2L (ORCPT ); Fri, 19 Jun 2020 09:28:11 -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 C552921582; Fri, 19 Jun 2020 13:28:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592573291; bh=woHoEU4qR1vtVDk6B4g7zX0biyS6r/lidqoPWMRgCmo=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=oWAUvvSiXpJTenQdhbrdO2GPm2gCTdYtqIZ+XfDE4nNQILPYHkEWQkHefSeZX5ej7 Q6ChI282ZFvsbrJk0hfvmXKhRFSnFuiVtPgIwkBv5hOFshKzeBjH3eoz9KV910p+m1 bcP8m0pxd0npcncMY85QRiKi5+PLtaWpE1V7VcYQ= Date: Fri, 19 Jun 2020 14:28:09 +0100 From: Mark Brown To: Douglas Anderson Cc: skakit@codeaurora.org, linux-spi@vger.kernel.org, Girish Mahadevan , linux-kernel@vger.kernel.org, Dilip Kota , linux-arm-msm@vger.kernel.org, swboyd@chromium.org, Andy Gross , Bjorn Andersson , Alok Chauhan In-Reply-To: <20200618150626.237027-1-dianders@chromium.org> References: <20200618150626.237027-1-dianders@chromium.org> Subject: Re: [PATCH v4 0/5] spi: spi-geni-qcom: Fixes / perf improvements Message-Id: <159257327821.5984.3382372060351730090.b4-ty@kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 18 Jun 2020 08:06:21 -0700, Douglas Anderson wrote: > This patch series is a new version of the previous patch posted: > [PATCH v2] spi: spi-geni-qcom: Speculative fix of "nobody cared" about interrupt > https://lore.kernel.org/r/20200317133653.v2.1.I752ebdcfd5e8bf0de06d66e767b8974932b3620e@changeid > > At this point I've done enough tracing to know that there was a real > race in the old code (not just weakly ordered memory problems) and > that should be fixed with the locking patches. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/4] spi: spi-geni-qcom: Mo' betta locking commit: 2ee471a1e28ec79fbfcdc8900ed0ed74132b0efe [2/4] spi: spi-geni-qcom: Check for error IRQs commit: e191a082d764e80a36c198da61fbf2851ebf425a [3/4] spi: spi-geni-qcom: Actually use our FIFO commit: 902481a78ee4173926dc59f060526dee21aeb7a8 [4/4] spi: spi-geni-qcom: Don't keep a local state variable commit: 7ba9bdcb91f694b0eaf486a825afd9c2d99532b7 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