soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Dmitry Osipenko <digetx@gmail.com>,
	Thierry Reding <treding@nvidia.com>,
	 Jonathan Hunter <jonathanh@nvidia.com>,
	Mark Brown <broonie@kernel.org>, SoC Team <soc@kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 "open list:TEGRA ARCHITECTURE SUPPORT"
	<linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v2] soc/tegra: Make regulator couplers depend on CONFIG_REGULATOR
Date: Mon, 2 Aug 2021 17:03:31 +0200	[thread overview]
Message-ID: <CAK8P3a1oVOqdyYUNBM8UiakEkznQ--SPEHVz4U0HQOMy4DiCbw@mail.gmail.com> (raw)
In-Reply-To: <YQgC/POOrX4t9hUN@orome.fritz.box>

On Mon, Aug 2, 2021 at 4:35 PM Thierry Reding <thierry.reding@gmail.com> wrote:
>
> On Thu, Jul 22, 2021 at 02:26:16AM +0300, Dmitry Osipenko wrote:
> > The regulator coupler drivers now use regulator-driver API function that
> > isn't available during compile-testing. Make regulator coupler drivers
> > dependent on CONFIG_REGULATOR in Kconfig.
> >
> > Fixes: 03978d42ed0d ("soc/tegra: regulators: Bump voltages on system reboot")
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> > ---
> >
> > Changelog:
> >
> > v2: - No changes. Re-sending to Arnd Bergmann and soc@kernel.org.
> >
> >  drivers/soc/tegra/Kconfig | 6 ++++--
> >  1 file changed, 4 insertions(+), 2 deletions(-)
>
> Seeing that Arnd hasn't picked this up yet, I've now applied it to the
> Tegra tree and plan to send out a PR for v5.14 later this week.

Sorry about the mixup. In fact I have just picked it up two hours ago.
If you have other fixes that are already in your fixes branch.

       Arnd

  reply	other threads:[~2021-08-02 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 23:26 [PATCH v2] soc/tegra: Make regulator couplers depend on CONFIG_REGULATOR Dmitry Osipenko
2021-07-22 10:49 ` Jon Hunter
2021-08-02 14:36 ` Thierry Reding
2021-08-02 15:03   ` Arnd Bergmann [this message]
2021-08-02 15:05     ` Arnd Bergmann
2021-08-02 16:23       ` Thierry Reding

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=CAK8P3a1oVOqdyYUNBM8UiakEkznQ--SPEHVz4U0HQOMy4DiCbw@mail.gmail.com \
    --to=arnd@kernel.org \
    --cc=broonie@kernel.org \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=soc@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=treding@nvidia.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).