[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <159101245057.15502.12546606590584178.b4-ty@kernel.org>
Date: Mon, 01 Jun 2020 12:54:10 +0100
From: Mark Brown <broonie@...nel.org>
To: "Jonathan, Bakker," <xc-racer2@...e.ca>,
kbuild test robot <lkp@...el.com>
Cc: kbuild-all@...ts.01.org, Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH regulator] regulator: max8998: max8998_set_current_limit() can be static
On Sat, 30 May 2020 21:03:14 +0800, kbuild test robot wrote:
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: max8998: max8998_set_current_limit() can be static
commit: 0b0c0bd818ef76a20f58c3cb1ac96a3056ccb681
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
Powered by blists - more mailing lists