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:     jiapeng.chong@linux.alibaba.com, lgirdwood@gmail.com
Cc:     abaci@linux.alibaba.com, linux-kernel@vger.kernel.org
In-Reply-To: <20220711034011.46096-1-jiapeng.chong@linux.alibaba.com>
References: <20220711034011.46096-1-jiapeng.chong@linux.alibaba.com>
Subject: Re: [PATCH] regulator: max597x: Remove unused including <linux/version.h>
Message-Id: <165756666336.1166849.14273128122593969453.b4-ty@kernel.org>
Date:   Mon, 11 Jul 2022 20:11:03 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 11 Jul 2022 11:40:11 +0800, Jiapeng Chong wrote:
> The patch makes sense but these are not compile warnings.
> They come from scripts/checkversion.pl, which can be called
> by 'make versioncheck', so I suppose that something in your
> build system is running 'make versioncheck'.
> 
> Eliminate the follow versioncheck warning:
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: max597x: Remove unused including <linux/version.h>
      commit: 3fec90048d3757fa4cedb598ff93d1cae23860e4

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