linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
To: Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Lee Jones <lee.jones@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
	ChiYuan Huang <cy_huang@richtek.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Christoph Fritz <chf.fritz@googlemail.com>,
	Axel Lin <axel.lin@ingics.com>,
	Vincent Whitchurch <vincent.whitchurch@axis.com>,
	Adam Ward <Adam.Ward.opensource@diasemi.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: bd71815: select CONFIG_ROHM_REGULATOR
Date: Wed, 21 Apr 2021 20:54:04 +0300	[thread overview]
Message-ID: <203a8c7449664512883153d4fb1a2c67882a40c4.camel@fi.rohmeurope.com> (raw)
In-Reply-To: <20210421145302.GA36124@sirena.org.uk>


On Wed, 2021-04-21 at 15:53 +0100, Mark Brown wrote:
> On Wed, Apr 21, 2021 at 03:54:27PM +0200, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> > 
> > The newly added driver is missing a dependency as shown by this
> > randconfig build failure:
> 
> This doesn't apply against current code, please check and resend.

I guess that the series which this change is patching was merged to
MFD-next but not yet to regulator tree. So, if I'm not mistaken the fix
needs to be applied to MFD - or wait until the rest of the series gets
into regulator tree.

In any case - thank you Arnd. This fix is correct and needed (reviewed
by me).

Best Regards
	Matti Vaittinen


  parent reply	other threads:[~2021-04-21 17:54 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 [this message]
2021-05-24 11:59 ` Mark Brown

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=203a8c7449664512883153d4fb1a2c67882a40c4.camel@fi.rohmeurope.com \
    --to=matti.vaittinen@fi.rohmeurope.com \
    --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=broonie@kernel.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=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).