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=-11.2 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 62D8EC433E9 for ; Wed, 13 Jan 2021 15:30:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 27CEF23382 for ; Wed, 13 Jan 2021 15:30:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727481AbhAMP34 (ORCPT ); Wed, 13 Jan 2021 10:29:56 -0500 Received: from mail.kernel.org ([198.145.29.99]:33988 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726779AbhAMP3z (ORCPT ); Wed, 13 Jan 2021 10:29:55 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 3A50023447; Wed, 13 Jan 2021 15:29:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1610551754; bh=Xa/4cpk6WRT4Je2DTLHBVP565AvV4yzmpFLqBfU3h34=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=GYNAm7OT26Qh+b/qFrq17EV+Q6O2kFxn1h21Q8WagYhUoAcUKQ0XWpsd0TIYNsOh3 2Rzn//LqNOU5R8QupPjWARjmQ2Rux0qfBascrMvCwQQUytMoOHB6z9NIa3Loa+xXgG M0YkHHoP2CN2qDueamDjwL6LUhRQq5zOyEtpAzFZQZkALMc/0dzOCRZkZNri5qrH/q hHsMTxownUbwzPDU08z8JQjbXO8AyDZ/VurwZ70cscHqmpR9tXtDQ7gowpqENnvOoM x5bGa3Nwoch0rIoalC8+PkUtVXbiEfX4B92HQLI/8scdjtiIAPy5O/TKOXUqcsZvgg Dyq17ZPimKKYA== From: Mark Brown To: Stephen Boyd Cc: Rajendra Nayak , linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org, linux-arm-msm@vger.kernel.org, Mukesh Kumar Savaliya , Douglas Anderson , Akash Asthana In-Reply-To: <20201213052948.308263-1-swboyd@chromium.org> References: <20201213052948.308263-1-swboyd@chromium.org> Subject: Re: [PATCH] spi: spi-qcom-qspi: Use irq trigger flags from firmware Message-Id: <161055171028.21847.6863638399695430601.b4-ty@kernel.org> Date: Wed, 13 Jan 2021 15:28:30 +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 Sat, 12 Dec 2020 21:29:48 -0800, Stephen Boyd wrote: > We don't need to force this to be trigger high here, as the firmware > properly configures the irq flags already. Drop it to save a line. Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: spi-qcom-qspi: Use irq trigger flags from firmware commit: eaecba8767835783bdd2f4e72406668cda7d8d54 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