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:     zhang.lyra@gmail.com, orsonzhai@gmail.com, lgirdwood@gmail.com,
        trix@redhat.com, baolin.wang7@gmail.com
Cc:     linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
In-Reply-To: <20220305162438.689442-1-trix@redhat.com>
References: <20220305162438.689442-1-trix@redhat.com>
Subject: Re: [PATCH] regulator: cleanup comments
Message-Id: <164668557274.3137513.14672957811652545659.b4-ty@kernel.org>
Date:   Mon, 07 Mar 2022 20:39:32 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Sat, 5 Mar 2022 08:24:38 -0800, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
> 
> For spdx
> Remove leading space, add space after //
> 
> Replacements
> overriden to overridden
> Calulate to Calculate
> addional to additional
> regulatior to regulator
> devive to device
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: cleanup comments
      commit: bbc7ba0fa06ab4aee26969a9454ca32e4a8fcb1c

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