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.0 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=ham 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 23B3EC5519F for ; Wed, 18 Nov 2020 21:00:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B0AEF2075B for ; Wed, 18 Nov 2020 21:00:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="EeMU8cTG" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726360AbgKRVAZ (ORCPT ); Wed, 18 Nov 2020 16:00:25 -0500 Received: from mail.kernel.org ([198.145.29.99]:55922 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725822AbgKRVAY (ORCPT ); Wed, 18 Nov 2020 16:00:24 -0500 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 80E39246AA; Wed, 18 Nov 2020 21:00:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1605733224; bh=spkhx3mTpbrol3ioqiZqCn/UIi+RkhiA4Wro0eYHxEQ=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=EeMU8cTGdzUJR9azgm0SOrPvB0s4X42/hQeUl94rRcUuTp6rHpD1AwJM2zdT3i5N3 Gq6hmSfgTCamiyhDYlf3ojlEDpgR+Yob+kZI4St106SaY2Ei5dG4U94W352xsnRaby tZkkex1wKCsk7dgkereJsY6Mpb5JuSqchK/wLYoU= Date: Wed, 18 Nov 2020 21:00:03 +0000 From: Mark Brown To: s.hauer@pengutronix.de, shawnguo@kernel.org, Zhang Qilong Cc: festevam@gmail.com, linux-imx@nxp.com, kernel@pengutronix.de, linux-spi@vger.kernel.org In-Reply-To: <20201106012421.95420-1-zhangqilong3@huawei.com> References: <20201106012421.95420-1-zhangqilong3@huawei.com> Subject: Re: [PATCH] spi: mxs: fix reference leak in mxs_spi_probe Message-Id: <160573320342.46706.17251700312199098743.b4-ty@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-spi@vger.kernel.org On Fri, 6 Nov 2020 09:24:21 +0800, Zhang Qilong wrote: > pm_runtime_get_sync will increment pm usage counter even it > failed. Forgetting to pm_runtime_put_noidle will result in > reference leak in mxs_spi_probe, so we should fix it. Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: mxs: fix reference leak in mxs_spi_probe commit: 03fc41afaa6549baa2dab7a84e1afaf5cadb5b18 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