Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     axel.lin@ingics.com
Cc:     cy_huang@richtek.com, linux-kernel@vger.kernel.org,
        lgirdwood@gmail.com
In-Reply-To: <20220404022514.449231-1-axel.lin@ingics.com>
References: <20220404022514.449231-1-axel.lin@ingics.com>
Subject: Re: [PATCH] regulator: rtq2134: Fix missing active_discharge_on setting
Message-Id: <164915113203.276837.10187918979668391155.b4-ty@kernel.org>
Date:   Tue, 05 Apr 2022 10:32:12 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 4 Apr 2022 10:25:14 +0800, Axel Lin wrote:
> The active_discharge_on setting was missed, so output discharge resistor
> is always disabled. Fix it.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: rtq2134: Fix missing active_discharge_on setting
      commit: 17049bf9de55a42ee96fd34520aff8a484677675

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