linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Arnd Bergmann <arnd@kernel.org>, Lee Jones <lee.jones@linaro.org>,
	Liam Girdwood <lgirdwood@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
	ChiYuan Huang <cy_huang@richtek.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Christoph Fritz <chf.fritz@googlemail.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Axel Lin <axel.lin@ingics.com>,
	linux-kernel@vger.kernel.org,
	Vincent Whitchurch <vincent.whitchurch@axis.com>,
	Adam Ward <Adam.Ward.opensource@diasemi.com>
Subject: Re: [PATCH] regulator: bd71815: select CONFIG_ROHM_REGULATOR
Date: Mon, 24 May 2021 12:59:52 +0100	[thread overview]
Message-ID: <162185754505.49496.2658967792826373332.b4-ty@kernel.org> (raw)
In-Reply-To: <20210421135433.3505561-1-arnd@kernel.org>

On Wed, 21 Apr 2021 15:54:27 +0200, Arnd Bergmann wrote:
> The newly added driver is missing a dependency as shown by this
> randconfig build failure:
> 
> arm-linux-gnueabi-ld: drivers/regulator/bd71815-regulator.o: in function `buck12_set_hw_dvs_levels':
> bd71815-regulator.c:(.text+0x4b6): undefined reference to `rohm_regulator_set_dvs_levels'

Applied to

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

Thanks!

[1/1] regulator: bd71815: select CONFIG_ROHM_REGULATOR
      commit: 5ba3747dbc9ade2d22a8f5bff3c928cb41d35030

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

      parent reply	other threads:[~2021-05-24 12:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 13:54 [PATCH] regulator: bd71815: select CONFIG_ROHM_REGULATOR Arnd Bergmann
2021-04-21 14:53 ` Mark Brown
2021-04-21 15:16   ` Arnd Bergmann
2021-04-21 15:19     ` Mark Brown
2021-04-21 17:54   ` Matti Vaittinen
2021-05-24 11:59 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162185754505.49496.2658967792826373332.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Adam.Ward.opensource@diasemi.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=axel.lin@ingics.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=chf.fritz@googlemail.com \
    --cc=cy_huang@richtek.com \
    --cc=krzk@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=vincent.whitchurch@axis.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).