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=-9.1 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 6FE15C433E3 for ; Tue, 28 Jul 2020 16:31:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4CD4C207F5 for ; Tue, 28 Jul 2020 16:31:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1595953899; bh=Y0EPEDkatR+hm/L7ATXN1AYrEx5ot0z2XTn8p1lfn9k=; h=Date:From:To:Cc:In-Reply-To:References:Subject:List-ID:From; b=IIuQbmOyOgKUlqy7v0ihtoUZOUAxChCZ6SW8wVQZ6ee18Y07H3bJxemwjeGbmXf88 N5W3XrvrcllpjPv7VTjPzv6CwW16faoAZ30gEbkE3ANofivXUUSL4c0/Lt9ZgS7vGB ImNp9P9H8Jq7RPKQ5WY1TjV1QOBuM0FBrvlaclv0= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731428AbgG1Qbj (ORCPT ); Tue, 28 Jul 2020 12:31:39 -0400 Received: from mail.kernel.org ([198.145.29.99]:47226 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731070AbgG1Qbi (ORCPT ); Tue, 28 Jul 2020 12:31:38 -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 D35132074F; Tue, 28 Jul 2020 16:31:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1595953898; bh=Y0EPEDkatR+hm/L7ATXN1AYrEx5ot0z2XTn8p1lfn9k=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=XsRz5Yx7Izihr2u416eX8IBjcMS96IE8jzSRuNznwvv0+/j95cjao21EeiSrmjeZ3 65A97uQibhrgzNSHlpxwWWbCufCCH30RGGIlVKkElq2eLBIvQnWU3Imy2fYJJZVZt6 hArbZ6K4Vaqk3RsJ82a0O9wfFKLSIN2lacNA8/0k= Date: Tue, 28 Jul 2020 17:31:20 +0100 From: Mark Brown To: Andy Shevchenko , Vaibhav Gupta , Bjorn Helgaas , Vaibhav Gupta , Bjorn Helgaas , Bjorn Helgaas Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org, linux-kernel-mentees@lists.linuxfoundation.org In-Reply-To: <20200727131742.82289-1-vaibhavgupta40@gmail.com> References: <20200727131742.82289-1-vaibhavgupta40@gmail.com> Subject: Re: [PATCH v2] spi: spi-topcliff-pch: drop call to wakeup-disable Message-Id: <159595388005.15302.1247752401935651695.b4-ty@kernel.org> Sender: linux-spi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-spi@vger.kernel.org On Mon, 27 Jul 2020 18:47:43 +0530, Vaibhav Gupta wrote: > Before generic upgrade, both .suspend() and .resume() were invoking > pci_enable_wake(pci_dev, PCI_D3hot, 0). Hence, disabling wakeup in both > states. (Normal trend is .suspend() enables and .resume() disables the > wakeup.) > > This was ambiguous and may be buggy. Instead of replicating the legacy > behavior, drop the wakeup-disable call. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: spi-topcliff-pch: drop call to wakeup-disable commit: 15b413d93ccd0d26c29f005df82c299c8f14cbd6 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