Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 11 Nov 2020 15:47:43 +0000
From:   Mark Brown <broonie@kernel.org>
To:     Sean Nyekjaer <sean@geanix.com>, linux-kernel@vger.kernel.org,
        yibin.gong@nxp.com
Cc:     stable@vger.kernel.org
In-Reply-To: <20201105114926.734553-1-sean@geanix.com>
References: <20201105114926.734553-1-sean@geanix.com>
Subject: Re: [PATCH] regualtor: pfuze100: limit pfuze-support-disable-sw to pfuze{100,200}
Message-Id: <160510965770.12262.8850331963860803288.b4-ty@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 5 Nov 2020 12:49:26 +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