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 33D63C388F9 for ; Wed, 11 Nov 2020 15:47:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C6A6720709 for ; Wed, 11 Nov 2020 15:47:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="wpi6K4zg" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727484AbgKKPry (ORCPT ); Wed, 11 Nov 2020 10:47:54 -0500 Received: from mail.kernel.org ([198.145.29.99]:43046 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726274AbgKKPrx (ORCPT ); Wed, 11 Nov 2020 10:47:53 -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 646362072C; Wed, 11 Nov 2020 15:47:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1605109673; bh=4xCQqP8hS7RB3yiV+asYpGivpGQ/TkgozNZlNZtmRGk=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=wpi6K4zgglUYnDJp2EHUyjZfyj+d+SZlo+nVKiZvnu8ErXqBrcMolBClzzOZ0UCRA 4BHQoAkd7vlL/ZvmnGJe6x35l6z9ZiE8oGSrhEdjymYmMTlFCvj57P+RzobGdbD6dY cRYoOG+OE+Ju7AXGc5uEq5toxtiPZ3HG+/BBA2dw= Date: Wed, 11 Nov 2020 15:47:37 +0000 From: Mark Brown To: Sean Nyekjaer , linux-kernel@vger.kernel.org, yibin.gong@nxp.com Cc: stable@vger.kernel.org In-Reply-To: <20201110174113.2066534-1-sean@geanix.com> References: <20201110174113.2066534-1-sean@geanix.com> Subject: Re: [PATCH v2] regulator: pfuze100: limit pfuze-support-disable-sw to pfuze{100,200} Message-Id: <160510965771.12262.14850696648694099172.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-kernel@vger.kernel.org On Tue, 10 Nov 2020 18:41:13 +0100, Sean Nyekjaer wrote: > Limit the fsl,pfuze-support-disable-sw to the pfuze100 and pfuze200 > variants. > When enabling fsl,pfuze-support-disable-sw and using a pfuze3000 or > pfuze3001, the driver would choose pfuze100_sw_disable_regulator_ops > instead of the newly introduced and correct pfuze3000_sw_regulator_ops. Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] regulator: pfuze100: limit pfuze-support-disable-sw to pfuze{100,200} commit: 365ec8b61689bd64d6a61e129e0319bf71336407 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